Project Context

Project Context

Use this skill when creating a reusable project context document for BA work or other prompt-driven collaboration.

Relationship to Copilot built-ins

• Use this skill before /plan when the main problem is missing business or organizational context rather than missing implementation detail.
• Use @file references to reuse the resulting context document in later Copilot CLI sessions.
• This skill creates durable project context. It does not replace execution planning or implementation review.

Interview domains

Capture only what the user actually knows across these domains:

1. Project overview
2. Stakeholders and audiences
3. Business context and domain
4. Domain terminology
5. Requirements context
6. Constraints and boundaries
7. Quality standards and preferences
8. AI interaction rules

Ask in small groups and avoid repeating information the user already provided.

Output contract

Produce a concise, reusable context artifact with these sections:

• Project
• Phase
• Project Overview
• Stakeholder Map
• Business Context
• Domain Terminology
• Scope Boundaries
• Constraints
• Political and Organizational Context
• Deliverable Standards
• AI Session Rules
• When In Doubt

Examples

• New project onboarding: Capture the project overview, stakeholders, terminology, constraints, and AI session rules, and leave [TO FILL: ...] placeholders where the user does not yet know the answer.
• Known political risk: When the user mentions a hidden approver or org tension, record it directly in the context artifact instead of softening it into generic process language.

Guardrails

• Include only user-provided facts.
• Use explicit placeholders like [TO FILL: ...] instead of inventing content.
• Compress answers into token-efficient reference notes.
• Surface political or organizational risks directly when the user mentions them.

Do Nots

• Do not turn this context-building workflow into implementation planning.
• Do not infer stakeholder motives, constraints, or standards the user never stated.
• Do not expand the artifact with verbose prose when concise reference notes are sufficient.

Closed Decisions

• This skill captures durable project context, not execution tasks or review findings.
• Only user-provided facts belong in the artifact; unknowns stay as explicit placeholders.
• The output section structure is fixed by this skill so later sessions can reuse it consistently.