Writing & Workflow Planning Skills

Archive a completed change after specs are merged and code is implemented. Use when both tracks are in terminal state.

View lifecycle status of all OpenSpec changes at a glance. Shows schema, version, specs-status, code-status, and created date. Use when agent or user wants to know what to work on next.

Use when compressing a YAML ADR into Y-Statement format. Use when creating a minimal-context summary of an architectural decision for agent search and retrieval.

Use this for every task, including after exiting plan mode. Declare what you're delivering and how to verify it, then hooks guide you through delivery and confirmation.

Implement tasks from a ratified OpenSpec change with lifecycle tracking. Use when code-status is ready or in-progress.

Initialize OpenSpec schemas in the current product. Copies bundled chaos-theory schemas from the ct plugin.

Principles for gap lifecycle management during spec critique and resolution. Use when creating, categorizing, resolving, or cleaning up gaps in gaps.md and resolved.md.

Merge change artifacts into product documentation with lifecycle tracking. Use when specs are ratified and ready to merge.

Create a new OpenSpec change with triage policy and gap tracking initialized. Use when starting a new feature, fix, or modification.

Ratify reviewed specs to unlock implementation. Use after the user has run critique/resolve CLI tools and specs are ready.

Use when reviewing proposed ADRs to decide whether to accept, reject, or defer. Use when an ADR has status: proposed and needs a decision.

Freeform design refinement for specs in draft state. Reads all artifacts holistically to identify cross-cutting design tensions, then revises artifacts directly. Use when specs need fundamental coherency work before structured critique/resolve polishing.

Use when OpenSpec artifacts need validation before proceeding. Use after creating or updating functional.md, technical.md, specs, or tasks.yaml.

Conceptual guidance for writing functional specifications. Use when creating or reviewing functional.md files.

Conceptual guidance for writing infrastructure specifications.

Use when writing BDD specs, feature files, or acceptance tests in Given-When-Then format. Use when editing .feature.md files or writing requirements with behavioral scenarios.

Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation.

Use when creating technical design documents, architecture documentation, or implementation specifications. Use when documenting technical decisions and component responsibilities.

Use when documenting low-overhead decisions during feature development. Use when a full ADR is overkill but the decision still needs to be recorded. Use when capturing quick design choices in code comments, PR descriptions, or lightweight decision logs.

Use when writing architectural decision records, documenting design choices, or recording technical decisions. Use when editing .adr.yaml files or adding decisions to an ADR file.