intent-driven-dev/intent-driven-template

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Use when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an acceptance stack, or implementing OpenSpec tasks that involve acceptance tests.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Use when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision history.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Use when explaining existing code architecture, visualizing a new system before detailed design, mapping software boundaries, or creating C4-style diagrams in ASCII or Mermaid.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Use when drafting, reviewing, or improving Gherkin, Cucumber scenarios, BDD acceptance criteria, feature examples, Scenario Outlines, Backgrounds, Rules, Doc Strings, Data Tables, tags, or Gherkin embedded in Markdown.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Use when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms, technical terms, or wording consistency across artifacts.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Use when running OpenSpec propose, continue, apply, verify, archive, or worktree workflows where proposal artifacts, branches, merges, or archive timing affect git history.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Use when a user or project explicitly adopts OpenSpec spec-as-source, fenced Gherkin specifications as executable acceptance tests, or acceptance-test-first OpenSpec tasks.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Use when implementing a change with test-driven development (TDD): work test-first through focused red-green cycles.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Use when rules or instructions mention "adversarial-authoring", "adversarial authoring", "must use adversarial-authoring skill", "model council", "cross-model review", or "mixture of models"; coordinates adversarial authoring and review subagents and records council notes.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

intent-driven-dev/intent-driven-template

Skill Claude CodeCodex

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.