メニュー
Continues Charted Coding work for a PR by routing to scaffold, red, or green based on design doc progress. Use when resuming work on a PR, continuing TDD after a break, or when the user invokes charted continue with a design doc and PR number.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Interviews the user section by section to collaboratively produce design documents. Use when creating a design doc, starting feature design, or when the user invokes the design command.
Progressively activates todo tests one at a time, updates implementation code until each passes (verified via Wallaby), checks off matching design doc progress, then moves to the next—following the design doc as the single source of truth.
Writes the next failing test based on provided design doc and existing todo tests
Reviews a design doc with expert sub-agents
Writes work-in-progress code and tests based on design doc
SOC 職業分類に基づく
| name | charted-continue |
| description | Continues Charted Coding work for a PR by routing to scaffold, red, or green based on design doc progress. Use when resuming work on a PR, continuing TDD after a break, or when the user invokes charted continue with a design doc and PR number. |
Read ${designDocPath}, inspect the state of PR #${prNumber}, and invoke exactly one downstream skill:
| Condition | Skill to invoke |
|---|---|
| Scaffolding not done | charted-scaffold |
| Next 🚧 test not implemented | charted-red |
| Next 🚧 test already implemented | charted-green |
In ${designDocPath}, find the section for PR #${prNumber} — a heading like # 🚧 PR#N - {title} or # PR#N - {title}.
Read its Tasks and Testing Strategy subsections. The design doc is the single source of truth for what belongs to this PR.
Scaffolding is done when all of the following hold for PR #${prNumber}:
### 🚧 {test_title} scenario has a matching it.todo("{test_title}", ...) in a test file (test names are lower case).@deprecated 🚧 work in progress or equivalent stubs).Scaffolding is not done if any expected test file or WIP source file is missing, or if it.todo stubs with design-doc step comments do not yet exist.
If scaffolding is not done → read and follow the charted-scaffold skill with ${designDocPath} and ${prNumber}. Stop.
In the PR's Testing Strategy, pick the first heading still marked ### 🚧 {test_title} (not ### ✅).
If every test is ### ✅, report that PR #${prNumber} is complete and stop.
Search the project for the it.todo whose name matches the pending test title (case-insensitive). Prefer the file under the component or unit named in the nearest ## {Component} heading above the scenario.
Record the path as testFilePath.
Open testFilePath and inspect the it.todo body for the pending test:
expect, inject, mount helpers, or other executable test code).Not implemented → read and follow the charted-red skill with ${designDocPath} and ${testFilePath}.
Implemented → read and follow the charted-green skill with ${designDocPath} and ${testFilePath}.