execute
Execute the implementation plan in spec/tasks.yaml task by task, validating each against its acceptance criteria and halting at checkpoints. Use this skill whenever the user asks to implement, execute, run, continue, or work on a plan; when a spec/ directory with tasks.yaml exists in the repo; when they reference task or phase IDs (task-N.M, phase-N); or when they ask to start the next task or phase.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- execute
- description
- Execute the implementation plan in spec/tasks.yaml task by task, validating each against its acceptance criteria and halting at checkpoints. Use this skill whenever the user asks to implement, execute, run, continue, or work on a plan; when a spec/ directory with tasks.yaml exists in the repo; when they reference task or phase IDs (task-N.M, phase-N); or when they ask to start the next task or phase.
02 资源文件 1
- 其他.intellij-skill-source24 B
03 SKILL.md 正文
Execute Skill
Execute the pre-approved implementation plan in spec/tasks.yaml task by task, validate each task, and halt at
checkpoints for approval.
This is the implementation phase of a spec-driven development workflow, after the plan has been generated and the review has gated it as ready.
Pipeline position: proposal → spec → criteria → rules → review → plan → execute
Role
You execute tasks in order, validate them, and report progress. You do not modify anything under /spec/ except
status.md. You do not skip tasks, reorder them, or proceed past checkpoints without explicit approval.
Inputs
- Plan: @file:spec/tasks.yaml (task list)
- Acceptance criteria: @file:spec/criteria.md (validation source)
- Technical constraints: @file:spec/rules.md (constraint set)
- Feature context: @file:spec/spec.md
- Pipeline verdict and risk hotspots: @file:spec/review.md
- Progress: @file:spec/status.md (you maintain this; create if missing)
Initialization
When starting work:
- Read
tasks.yaml. This is your task list. - Read
criteria.mdandrules.md. - Read
spec.mdfor feature context andreview.mdfor risk hotspots that map to specific tasks. - Read
status.mdto find your position. If it doesn't exist, create it withphase-1/task-1.1asNOT_STARTED. - Set
current_taskto the first task with statusNOT_STARTED.
Execution Loop
For each task:
-
Verify prerequisites. For every
task_idintask.depends_on, confirm its status isCOMPLETEinstatus.md. If not, halt with a Blocker report. -
Mark in progress. Update
status.md: set the task toIN_PROGRESS. -
Execute. Read the task's
description,artifact,covers.acs, andcovers.rules. Produce or update the artifact, plus any supporting files (tests, fixtures, configs) needed to satisfy validation. Apply every constraint listed incovers.rules. Do not modify files unrelated to this task. -
Validate. Run the check described in
task.validation. Then verify every AC incovers.acsis satisfied, typically through passing tests or behavioral checks againstcriteria.md. If validation fails, take up to two corrective attempts. Each attempt must be a different approach, not a re-run of the same code. If still failing after two attempts, halt with a Blocker report. -
Mark complete. Update
status.md: set the task toCOMPLETE. Record any non-obvious decisions in the notes. -
Advance. If more tasks remain in the phase, set
current_taskto the next one. If this was the last task of the phase, generate a Checkpoint report and halt for approval.
When all phases complete, generate a Completion report.
Approval Responses
After a Checkpoint report, wait for one of:
APPROVED: proceed to the next phase.APPROVED WITH NOTES: <notes>: record notes instatus.md, then proceed.REVISE: task-N.M - <instructions>: apply the revision to the named task, re-validate, then resume.ROLLBACK: task-N.M: mark the named taskNOT_STARTED, undo its artifact, then resume from there.BLOCKED: <reason>: record blocker instatus.mdand halt.
After a Blocker report, wait for one of:
PROCEED WITH: <option number>: continue using the specified option from the report.PROCEED WITH: <custom instructions>: continue using user-provided guidance.ABORT TASK: skip this task and adjust the plan.
Status File Format
Maintain spec/status.md with only the delta from tasks.yaml. Everything else is derivable.
# Status: <feature>
## Current
- Task: task-N.M
- Status: IN_PROGRESS | NOT_STARTED | BLOCKED
## Completed
- task-1.1
- task-1.2
## Phase Approvals
- phase-1: APPROVED
- phase-2: PENDING
## Blockers
(empty if none)
## Deviations
(approved deviations from plan, with task ID and reason)
## Notes
(non-obvious decisions, per task)
Checkpoint Report
# Checkpoint: phase-N complete
## Summary
- Phase: phase-N, <name>
- Tasks: <n>/<n> complete
## Artifacts
| File | Purpose |
|--------|------------|
| <path> | <one-line> |
## AC Coverage (this phase)
| AC | Status | Verified in |
|------|-----------|----------------|
| AC-1 | satisfied | <file or test> |
## Validation
- Compilation: PASS | FAIL
- Tests: <n>/<n> passing
- Constraints (this phase's RULES): <n>/<n> satisfied
## Notes
<ambiguities resolved, deviations, concerns; empty if none>
CHECKPOINT REACHED. AWAITING APPROVAL.
Blocker Report
# BLOCKED: task-N.M
## Type
SPEC_AMBIGUITY | SPEC_CONFLICT | TECHNICAL | VALIDATION_FAILURE | DEPENDENCY
## Summary
<one sentence>
## Details
<full explanation>
## Evidence
<code, error messages, spec quotes>
## Attempted Solutions
1. <what you tried> → <result>
2. <what you tried> → <result>
## Options
1. <option>
- Impact: <plan, timeline, architecture>
- Tradeoff: <pros, cons>
2. <option>
- Impact: <...>
- Tradeoff: <...>
## Recommendation
<which option and why>
BLOCKED. AWAITING RESOLUTION.
Completion Report
# Feature Complete: <feature>
## Summary
- Phases: <n>/<n> complete
- Tasks: <n>/<n> complete
- ACs satisfied: <n>/<n>
- RULES applied: <n>/<n>
## Coverage
| AC | Implemented in |
|------|----------------|
| AC-1 | <file or test> |
## Deviations from Plan
<deviations approved during execution; empty if none>
## Open Items
<anything intentionally deferred, with reason>
Rules
- The
/spec/directory is read-only during implementation. The single exception isstatus.md, which you maintain. - Do not skip tasks or reorder within a phase.
- Do not proceed past a checkpoint without an approval response.
- Do not proceed when blocked without a resolution response.
- A task may touch supporting files (tests, fixtures, configs) needed to satisfy
validation, but must not modify files unrelated to the task'sartifactand coverage. - Record non-obvious decisions in the per-task notes in
status.md.
04 同仓库更多 Skills
grilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
grill-me
A relentless interview to sharpen a plan or design.
tasks
Generate an implementation task list from validated spec artifacts
spec-review
Stress-test the spec pipeline outputs against each other and the codebase before implementation begins
rules
Capture feature-level design decisions and the technical constraints that follow, traceable to acceptance criteria
criteria
Translate the spec into a complete, traceable set of acceptance criteria in EARS form