Analyze Context Skill

Goal: Stop guessing. Start knowing.

The Protocol

1. Instruction Discovery

You must read the following global instructions to ground yourself:

• .github/instructions/architecture.instructions.md (Layers & Rules)
• .github/instructions/conventions.instructions.md (Naming & patterns)
• .github/instructions/dependencies.instructions.md (NuGet & 3rd party)

Conditional Reads:

• If Database changes: .github/instructions/marten.models.instructions.md
• If New Accessor: .github/instructions/accessor-implementation.instructions.md
• If Testing: .github/instructions/integration.tests.instructions.md

2. Pattern Matching (The "Reference Implementation")

You must find one specific file in the existing codebase that solves a similar problem to the current story.

Example: "This story adds a new profile. EmployeePersonalProfile.cs is the reference."

Action: Read that file. You will need to cite it later.

3. Architecture Context

Identify the Host, Manager, Engine, and Accessor involved.

Verify layer directions (e.g., Engine → Accessor, NEVER Accessor → Manager).

4. Output Generation

Create planning/context-brief.md in the story folder.

Content Requirements for context-brief.md:

1. Governing Instructions: List the specific .github/instructions files that apply.
2. Reference Pattern: The path/to/existing/code.cs you will mimic.
3. Architectural Touchpoints: List the specific projects/services involved.
4. Reflexion: A 1-sentence statement confirming you have read the reference file.