coograph: Skill for Claude Code

Propose a new change — investigate the codebase, create all artifacts, and wait for approval before implementing.

---

Step 1: Understand what to build

If no input was provided, ask the user:

"What change do you want to work on? Describe what you want to build or fix."

From their description, derive a kebab-case slug (e.g., "add user auth"). Wait for their answer before proceeding.

Step 2: Investigate the codebase

Before writing anything:

1. 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) for rules, conventions and stack, if not already loaded.
2. Search for related files, existing patterns, integration points, and risks relevant to this change.
3. Identify which files will likely be modified or created.

Step 3: Create the change directory

Create openspec/changes/<YYYY-MM-DD>-<slug>/ using today's date.

Create .openspec.yaml with:

schema: spec-driven
name: <slug>
created: <YYYY-MM-DD>

Step 4: Create proposal.md

Write openspec/changes/<slug>/proposal.md:

# Proposal: <human-readable title>

## Why
[Problem being solved and motivation]

## Goals
- [Concrete, measurable deliverable]

## Non-Goals
- [Explicit out-of-scope items]

## Decisions
- [Key design decisions and why they were made]

## Impact
- Files to modify: [specific file paths]
- Files to create: [specific file paths]
- Dependencies affected: [if any]

## Risks
- [Risk]: [mitigation]

Step 5: Create specs//spec.md

Write openspec/changes/<slug>/specs/<capability>/spec.md:

# Spec: <capability name>

## Requirements
- [Requirement 1]
- [Requirement 2]

## Scenarios
### Scenario: <description>
- Given: [precondition]
- When: [action]
- Then: [expected outcome]

Step 6: Create tasks.md

Write openspec/changes/<slug>/tasks.md with 3-8 tasks grouped by logical unit (not per-file):

# Tasks: <change-name>

- [ ] **<Logical group title>** — [description of what this group accomplishes]
  - Files: [file paths]
  - Acceptance: [measurable criteria]

- [ ] **Verification** — Run quality gates and confirm all acceptance criteria are met