Use when you need the exact format, lifecycle, or strict rules for the agile-team-v2 code markers — // AC: + // TODO(impl- , ac- ) + panic(\"not implemented\") (inlined by the architect during scaffolding above each scaffolded function body that maps to an acceptance criterion) and // SCENARIO: + // TODO(impl- , scenario- ) + t.Skip(\"not implemented\") (inlined by the PM in passe 2 inside business test skeletons under pmtestterritories). Covers the strict marker format that check.sh enforces (kebab-case feature-slug, three-digit zero-padded NNN, exact ac- or scenario- prefix), the pmtestterritories glob block declared in .architecture/CONVENTIONS.md (where // SCENARIO: markers may live), the seven-step marker lifecycle (architect scaffolds → PM passe 2 → red → green → e2e-tester → reviewer pass 2 → TODO removed when feature done while // AC: stays as permanent record), and the marker-based task lookup procedure (grep -rn TODO(impl-...) to locate the scaffolded body or test skeleton — replaces v1 TASK.md/TASK-red.md/TASK-green.md/SCAFFOLD.md prose intermediaries). Loaded by every agent that touches markers in any way: architect (writes // AC:), PM (writes // SCENARIO:), red (locates AC and writes assertions), green (reads AC and removes TODO when done), e2e-tester (locates SCENARIO and writes e2e assertions), reviewer (Pass 2 verifies marker ↔ user-journey alignment), sprint-planner (lists tasks by code marker in SPRINT.md). Bug-detective is the only agent that does not load this skill — it reads // AC: from committed code post-mortem without needing the format spec.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryContent & writingStars0
About this skill
Use when you need the exact format, lifecycle, or strict rules for the agile-team-v2 code markers — // AC: + // TODO(impl- , ac- ) + panic(\"not implemented\") (inlined by the architect during scaffolding above each scaffolded function body that maps to an acceptance criterion) and // SCENARIO: + // TODO(impl- , scenario- ) + t.Skip(\"not implemented\") (inlined by the PM in passe 2 inside business test skeletons under pmtestterritories). Covers the strict marker format that check.sh enforces (kebab-case feature-slug, three-digit zero-padded NNN, exact ac- or scenario- prefix), the pmtestterritories glob block declared in .architecture/CONVENTIONS.md (where // SCENARIO: markers may live), the seven-step marker lifecycle (architect scaffolds → PM passe 2 → red → green → e2e-tester → reviewer pass 2 → TODO removed when feature done while // AC: stays as permanent record), and the marker-based task lookup procedure (grep -rn TODO(impl-...) to locate the scaffolded body or test skeleton — replaces v1 TASK.md/TASK-red.md/TASK-green.md/SCAFFOLD.md prose intermediaries). Loaded by every agent that touches markers in any way: architect (writes // AC:), PM (writes // SCENARIO:), red (locates AC and writes assertions), green (reads AC and removes TODO when done), e2e-tester (locates SCENARIO and writes e2e assertions), reviewer (Pass 2 verifies marker ↔ user-journey alignment), sprint-planner (lists tasks by code marker in SPRINT.md). Bug-detective is the only agent that does not load this skill — it reads // AC: from committed code post-mortem without needing the format spec.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Use this skill whenever you need the exact format, lifecycle, or strict rules for the agile-team-v2 code markers — `// AC: <criterion>` + `// TODO(impl-<feature-slug>, ac-<NNN>)` + `panic(\"not implemented\")` (inlined by the architect during scaffolding above each scaffolded function body that maps to an acceptance criterion) and `// SCENARIO: <narrative>` + `// TODO(impl-<feature-slug>, scenario-<NNN>)` + `t.Skip(\"not implemented\")` (inlined by the PM in passe 2 inside business test skeletons under `pm_test_territories`). Covers the strict marker format that `check.sh` enforces (kebab-case feature-slug, three-digit zero-padded NNN, exact `ac-` or `scenario-` prefix), the `pm_test_territories` glob block declared in `.architecture/CONVENTIONS.md` (where `// SCENARIO:` markers may live), the seven-step marker lifecycle (architect scaffolds → PM passe 2 → red → green → e2e-tester → reviewer pass 2 → TODO removed when feature done while `// AC:` stays as permanent record), and the marker-based task lookup procedure (`grep -rn TODO(impl-...)` to locate the scaffolded body or test skeleton — replaces v1 TASK.md/TASK-red.md/TASK-green.md/SCAFFOLD.md prose intermediaries). Loaded by every agent that touches markers in any way: architect (writes `// AC:`), PM (writes `// SCENARIO:`), red (locates AC and writes assertions), green (reads AC and removes TODO when done), e2e-tester (locates SCENARIO and writes e2e assertions), reviewer (Pass 2 verifies marker ↔ user-journey alignment), sprint-planner (lists tasks by code marker in SPRINT.md). Bug-detective is the only agent that does not load this skill — it reads `// AC:` from committed code post-mortem without needing the format spec.
About this listing
Category
Content & writing
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI