Why This Matters

Phase 1 gave you the foundation; Phase 2 is where you become an operator. This preview helps you pick the right starting arc and reinforces what you've learned before the leap.

Concept Explained

Phase 2 has 8 arcs: steering, workspace-scale, Copilot Spaces, multi-model strategy, quality control, tooling, CLI, projects. Each builds on Phase 1 foundations.

How It Works

Read the preview of each arc. Identify which 2–3 arcs most directly address your current needs. Plan to start with those. Reinforce Phase 1 by re-reading BE-13, BE-31, BE-49 before starting Phase 2.

Step-by-Step Tutorial

1. Read arc previews

2. Pick 2–3 starting arcs

3. Reinforce Phase 1

4. Plan first 5 lessons

5. Take the leap

Real-World Example

A developer previewed Phase 2 arcs and identified CLI + workspace-scale as most relevant (they do DevOps and work in large repos). They re-read BE-13 and BE-31, then started Phase 2 with IN-41 (CLI) and IN-09 (@workspace). Within 2 weeks, their daily Copilot usage transformed from inline-only to multi-surface.

Example Prompts / Commands / Code

Steering (IN-01 to IN-08):
  Context engineering, few-shot patterns, output schemas, prompt templates.
  Who: anyone wanting deeper control over Copilot output.

Workspace-Scale (IN-09 to IN-16):
  @workspace deep dive, attachments, cross-file refactors, hallucination reduction.
  Who: developers in medium-to-large repos.

Copilot Spaces (IN-17 to IN-22):
  Build scoped context containers for multi-repo or docs+code work.
  Who: anyone working across repos or with external docs.

Multi-Model Strategy (IN-23 to IN-28):
  GPT-5 vs Claude vs Gemini, cost/quality trade-offs, auto-model.
  Who: anyone on Pro+ wanting conscious model selection.

Quality Control (IN-29 to IN-34):
  Verification patterns, self-checking prompts, eval sets.
  Who: anyone shipping Copilot-assisted code to production.

Tooling (IN-35 to IN-40):
  Extensions, MCP, custom slash commands.
  Who: anyone wanting to extend Copilot's reach.

CLI (IN-41 to IN-46):
  The new copilot CLI, terminal workflows, multi-file edits.
  Who: DevOps, infra engineers, terminal-heavy developers.

Projects (IN-47 to IN-52):
  Prompt-template library, PR-description generator, test pipeline, etc.
  Who: everyone — projects are the highest-leverage learning.

Common Mistakes

• Starting Phase 2 without reinforcing Phase 1.
• Reading all arcs sequentially — pick what you need.
• Skipping the projects arc — projects cement learning.

Best Practices

• Preview each arc; pick 2–3 most relevant.
• Re-read BE-13, BE-31, BE-49 before starting.
• Plan your first 5 Phase 2 lessons.
• Include at least one project in your first month.
• Adjust as you go — the plan is a starting point.

Troubleshooting

Practical Exercise

Professional Challenge

Frequently Asked Questions

Further Reading

• Copilot learning paths

Official References

• Copilot docs

Related lessons: BE-50, IN-01