coograph: Skill for Claude Code

Start work on a new ticket — run pre-flight, investigate, and propose a change.

---

Step 1: Pre-flight checks

Before doing anything else:

1. Code-graph availability — call get_minimal_context with a one-line summary of the ticket. Record whether code-graph is available. If available, use it for ALL navigation in subsequent steps.
2. Check for in-progress work — list openspec/changes/ (skip archive/). If an existing OpenSpec overlaps with this ticket, stop and ask: "There's an in-progress change <name> — is this ticket related, or should I start fresh?"
3. Read conventions — read AGENTS.md § Hard rules and .github/copilot-instructions.md (when AGENTS.md has no Hard rules section, .github/copilot-instructions.md holds them all) if not already loaded.

Step 2: Parse the ticket

Extract from the user's input:

• Title/summary — one-line description
• Requirements — what needs to be built or changed
• Acceptance criteria — if provided
• Linked references — URLs, ticket IDs, file paths mentioned

If the ticket is vague (no specific files, unclear deliverable, touches 3+ areas), note this — it affects Step 3.

Step 3: Investigate the codebase

Use code-graph tools (or fallback chain) to:

1. Identify files and modules affected by the ticket
2. Read relevant source code to understand current behavior
3. Find existing patterns the implementation should follow
4. Surface risks, dependencies, and integration points

Scope the investigation to the ticket. Don't audit the entire codebase.

If the ticket is vague or complex (identified in Step 2):

• Run deeper investigation
• Ask the user focused clarifying questions (one at a time, with choices when possible)
• Do NOT proceed to Step 4 until requirements are clear

If the ticket is specific and well-scoped:

• Investigation can be brief
• Proceed directly to Step 4

Step 3b: Models, asked once

Read the models block in openspec/config.yaml. If mode is anything other than unset, skip this step entirely and never mention it.