القائمة
Continue working through a project plan. Finds the next unchecked task and begins implementation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Write an implementation plan to docs/plans/. ALWAYS use this skill — never hand-roll a plan by mimicking files in docs/. Use when the user wants to create a project/implementation plan, when a plan discussed in chat should be persisted, or says /project-plan. Guarantees a spec exists, invoking to-spec if absent. Decomposes into vertical slices with Blocked-by edges, points to the spec for acceptance criteria, and extracts ADRs via to-adr.
Parse test failure output and diagnose root causes in a read-only background subagent, then fix the failures interactively in the main thread. Use when the user shares test output or says "tests fail". Default output path is /tmp/output.
Surface systemic patterns from an investigation as codified conventions or anti-patterns.
Architect a change from idea to actionable artifacts — bootstrap project instructions, research deeply, write a spec, then an implementation plan, each delegated to its skill. Use when the user wants to research a topic, explore a repo, write a spec, create a project plan, or says /architect.
Research a topic or repository deeply and produce a reference document under `docs/research/`. Handles two modes: code research (repo by URL, `org/repo`, or bare name — e.g. "check the spotless repo", "look at github.com/fastly/spotless") and topic research (concepts, technologies, patterns). Use when the user wants to research something, explore a repo, or says /research.
Elicit the user's intent before starting work. Use when a request is vague, when kicking off a new task, when another skill hits a vague request and needs to clarify it, or when the user says "help me with this", "I need something", "let's work on...", "draft a task", or /task.
| name | next-task |
| description | Continue working through a project plan. Finds the next unchecked task and begins implementation. |
| disable-model-invocation | true |
Resume work from a project plan, in the main thread.
find docs/plans -maxdepth 1 -name '*.md' ! -name 'README.md' -newer docs/plans/completed 2>/dev/null | head -10 || find docs/plans -maxdepth 1 -name '*.md' ! -name 'README.md' 2>/dev/null | head -10Identify the project plan. Use the user's file if specified; otherwise pick from the context above. If multiple non-completed plans exist, present them as a numbered list with filenames and ask which to use. Always state the plan you'll use and wait for confirmation.
I'll work from docs/plans/cross-team-routing-isolation.md.
OK, or did you have a different plan in mind?
Read the plan and find the first actionable unchecked task (- [ ]) in
document order. A task is actionable unless its slice's - **Blocked by**:
line names a slice that still has unchecked tasks — skip a blocked task and
keep scanning. Plans without Blocked by (older phase-based plans) never
block, so the first unchecked task wins. If every remaining task is blocked,
report which slice is next and what it waits on, then stop.
Announce the task:
Next up: Task 2.3 — Add cache invalidation for config
updates
Execute it directly in the main thread:
make test when done.docs/**/*.md or **/README.md if the change alters
behavior, public APIs, or usage patterns.Once verified (tests pass, work done), mark it complete before finishing:
- [ ] to - [x] in the plan file./commit.- [x].