Run any Skill in Manus with one click

spec-loop-implementation-flow

Stars33

Forks1

UpdatedJune 30, 2026 at 16:37

Use this skill after execution approval for implementation work in an approved chat-only or task-file task. It governs implementation-time routing, canonical task updates, and the final review checkpoint.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

dpolivaev

dpolivaev/spec-loop

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

4 files

SKILL.md

readonly

name	spec-loop-implementation-flow
description	Use this skill after execution approval for implementation work in an approved chat-only or task-file task. It governs implementation-time routing, canonical task updates, and the final review checkpoint.

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

Read spec-loop-plan-task/SKILL.md and the files it requires.
Choose the active path:
- task-file path = an approved task file controls the current increment
- chat-only path = an approved canonical chat-only task in chat controls the current increment
Then read:
- implementation-flow-guidance.md
- the matching path companion for the active path:
  - chat-only-path-guidance.md
  - task-file-path-guidance.md

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.

More from this repository

same repository

spec-loop-prepare-execution-approval

dpolivaev/spec-loop

Mandatory only on the task-file path of `spec-loop-plan-task`. Use when an active task file already exists and the next user-facing action would otherwise present task-file work for evaluation, feedback, review, or execution approval.

2026-07-0233

spec-loop-plan-task

dpolivaev/spec-loop

Choose the planning form for new work and plan it before execution. Use this skill to decide whether the work is taskless, chat-only, a task file, a task file with subtasks, or multiple task files / backlog items, and to create the needed plan for non-trivial implementation work or investigation work that needs its own task.

2026-06-3033

spec-loop-assess-pull-request

dpolivaev/spec-loop

Optional skill. Reconstruct a human-review-preparation file from an existing pull request, merge request, branch diff, or commit range in a repository the user trusts. Use when the user wants retrospective understanding of already-implemented changes, AI-side assessment and recommendations, and an optional provider-specific sharing variant written to a local file when needed.

2026-06-3033

spec-loop-write-glossary

dpolivaev/spec-loop

Create or update a project glossary in the Spec Loop AsciiDoc glossary format. Use when the user, project instructions, or `spec-loop-plan-task` already requires project glossary work. This skill is mandatory for AsciiDoc project glossaries unless the user explicitly opts out for the current project or session.

2026-06-3033

spec-loop-clarify-task

dpolivaev/spec-loop

Engage the User to resolve important open decisions in Spec Loop work, including tasks, plans, design updates, work breakdowns, implementation checkpoints, and ADR drafting. Use when the user asks to clarify, compare options, discuss criteria, or stress-test, or when different answers could materially change scope, behavior, policy, constraints, route, Design, Test specification, or ADR content. Provides mandatory decision screening for workflows that require it before dependent Spec Loop content is written or revised. Also use for general grilling when explicitly selected.

2026-06-2933

spec-loop-plan-work-breakdown

dpolivaev/spec-loop

Create or revise file-based Spec Loop work breakdown artifacts for task-file work that uses subtasks or multiple task files / backlog items.

2026-06-2933

name	spec-loop-implementation-flow
description	Use this skill after execution approval for implementation work in an approved chat-only or task-file task. It governs implementation-time routing, canonical task updates, and the final review checkpoint.

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

Read spec-loop-plan-task/SKILL.md and the files it requires.
Choose the active path:
- task-file path = an approved task file controls the current increment
- chat-only path = an approved canonical chat-only task in chat controls the current increment
Then read:
- implementation-flow-guidance.md
- the matching path companion for the active path:
  - chat-only-path-guidance.md
  - task-file-path-guidance.md

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.