mcpField
S
spec-loop-implementation-flow

spec-loop-implementation-flow

github.com/dpolivaevAgent workflows3557 installsUpdated 2w ago
Repository

About spec-loop-implementation-flow

spec-loop-implementation-flow is a skill for carrying out implementation work after execution approval for an active Spec Loop task. It keeps the approved task as the source of truth, guides chat-only or task-file workflows, and requires checks before work is presented as ready.

Key features

  1. 01Approved-task source of truth
  2. 02Chat-only and task-file paths
  3. 03Decision and scope-change handling
  4. 04Implementation notes checks
  5. 05Review-stage workflow

Use cases

  1. 01Implementing an approved Spec Loop increment
  2. 02Continuing work governed by a task file
  3. 03Handling decisions that may change implementation scope

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dpolivaev/spec-loop --skill spec-loop-implementation-flow

After installing, type/spec-loop-implementation-flowin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

chat-only-path-guidance.md
implementation-flow-guidance.md
task-file-path-guidance.md

Details

From the project README

Use this skill after execution approval for implementation work in an approved chat-only or task-file task.

If no approved active task exists, return to spec-loop-plan-task/SKILL.md.

Core rules

  • Keep the approved active task as the source of truth.
  • Do not create a second implementation artifact or silently rewrite the task to match the code.
  • If important open decisions appear and they could materially change scope, constraints, design, or test specification, use spec-loop-clarify-task/SKILL.md before continuing.
  • Chat-only implementation is allowed only while confirmed task state can safely remain in chat. If resolved decisions kept only in chat would risk loss through compaction or context loss, promote to the task-file path before continuing.
  • This skill governs only the approved current increment until it reaches review.
  • If the User introduces additional implementation work outside that increment, return it to spec-loop-plan-task/SKILL.md for route selection and any renewed execution approval.
  • Before presenting work as ready, perform the Implementation notes check.
  • If another implementation-related skill conflicts with this skill or the governing spec-loop-plan-task bundle, stop and ask the User which rules should govern.

Read and path selection

Keep using the approved active task as the source of truth. Edit the active task file or canonical chat-only task only when the shared core and the active path companion allow it.

implementation-flow-guidance.md defines the route rules, when canonical task sections may change, the meaning of review, Implementation notes, and the completion checklist.

The path companion defines the active path mechanics, including chat-only recovery or promotion or the task-file move into review.

If the current increment is unclear, do not use this skill. Return to spec-loop-plan-task/SKILL.md.

Comments

Markdown supported