name	spec
description	Phase 1 planning — read docs, read source, write implementation plan
argument-hint	<task-description>
user-invocable	true
allowed-tools	["Read","Glob","Grep","Bash"]

Phase 1: Spec (Plan)

Before writing any code, produce a plan for the requested change.

Read the relevant documentation in documentation/.
Read every source file you intend to modify.
Write a concise plan:
- What changes and why.
- Which files are affected.
- Any risks or open questions.
Document key design decisions and their rationale. If there are multiple viable approaches, state which one you chose and why. This prevents oscillating between approaches during implementation.
Present the plan and wait for human approval before proceeding.

Do NOT skip to implementation. A good plan lets you one-shot Phase 2.

User request: $ARGUMENTS

Más de este repositorio

mismo repositorio

Adversarial code review — find bugs, style issues, SDK misuse, then challenge findings

Pre-PR pipeline — version bump check, changelog, lint, build, and diff summary

Phase 3 review — find unnecessary code, abstractions, and dead paths, then simplify

Phase 4 verification — lint check then full dual-backend build verification

Adversarial code review with two passes. First finds issues, then challenges each finding to eliminate false positives. Use before merging.

Review and simplify recent code changes. Remove unnecessary abstractions, dead code, and complexity while preserving behavior.

name	spec
description	Phase 1 planning — read docs, read source, write implementation plan
argument-hint	<task-description>
user-invocable	true
allowed-tools	["Read","Glob","Grep","Bash"]

Phase 1: Spec (Plan)

Before writing any code, produce a plan for the requested change.

Read the relevant documentation in documentation/.
Read every source file you intend to modify.
Write a concise plan:
- What changes and why.
- Which files are affected.
- Any risks or open questions.
Document key design decisions and their rationale. If there are multiple viable approaches, state which one you chose and why. This prevents oscillating between approaches during implementation.
Present the plan and wait for human approval before proceeding.

Do NOT skip to implementation. A good plan lets you one-shot Phase 2.

User request: $ARGUMENTS