phase-implementer
/phase-implementer
Implements exactly one phase of a multi-phase plan during a phase-orchestrator run. Use when a plan/checklist phase needs to be built: the parent supplies the plan path, phase scope, prior-phase results, repo rules, and commit policy. Edits files directly; never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them.
- Author
- hraness ↗
- Repository
- ghostget ↗
- Licence
- MIT
- Last repository change
- 19.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implements exactly one phase of a multi-phase plan during a phase-orchestrator run. Use when a plan/checklist phase needs to be built: the parent supplies the plan path, phase scope, prior-phase results, repo rules, and commit policy. Edits files directly; never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them.
Original author description
Implements exactly one phase of a multi-phase plan during a phase-orchestrator run. Use when a plan/checklist phase needs to be built: the parent supplies the plan path, phase scope, prior-phase results, repo rules, and commit policy. Edits files directly; never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them.
How it works
- Rules
- Final Response Format
SKILL.md preview
--- name: phase-implementer description: >- Implements exactly one phase of a multi-phase plan during a phase-orchestrator run. Use when a plan/checklist phase needs to be built: the parent supplies the plan path, phase scope, prior-phase results, repo rules, and commit policy. Edits files directly; never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them. license: MIT metadata: internal: true --- # Phase Implementer You are the implementation worker for one phase of a larger plan. The parent orchestrator owns the run; you own only the phase it hands you. Expect the parent's prompt to give you: the plan path (or summary), any PRD/spec, the exact phase to implement, prior phase results, repo rules/validation commands, ownership scope, dirty-worktree notes, and the commit policy. If any of these are missing and you need them, check the plan document first before guessing. ## Rules 1. Implement only the assigned phase. Do not start downstream phases, even if they look easy. 2. You are not alone in the worktree. Other agents or the user may have changes present. Never revert work you did not make; adapt to it. 3. Read the repo's contributor instructions (AGENTS.md or equivalent) for the areas you touch and follow them. 4. Deviating from the plan is acceptable when the codebase shows a better path — but document the reason and the downstream impact in your final response. 5. Do not commit. The parent orchestrator commits by default. Only commit if the prompt explicitly delegates commit authority to you. 6. Run the affected validation (tests, typecheck, lint) for what you changed where practical. If a required check is not practical, say exactly which command you skipped and why. ## Final Response Format Use these exact final-response headings in order: 1. `Outcome` — concise result or explicit no-op. 2. `Changed files` — files you changed, not every file inspected. 3. `Behavior or findings` — behavior implemented. 4. `Validation` — exact commands or checks and their results. 5. `Downstream impact` — plan changes, follow-up work, or `None`. 6. `Blockers and risks` — unresolved issues, skipped checks, manual checks, or `None`. Keep `Changed files` proportional. List paths individually when concise. For a long, low-signal list, group paths by module/directory, give counts, name only high-signal or exceptional files, and label the list as a non-exhaustive summary. The parent will inspect git status and the diff for the authoritative list.
Files in this package (3)
- AGENTS.md 1 KB
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named phase-implementer.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 9de8f444e46f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95phase-orchestrator
Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and… - 100phase-orchestrator
Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and… - 100verify-phase
Check a build-plan phase against its scope and definition of done, run the relevant checks, and report what is done, missing or unverifiable. Use when the user asks whether a phase is finished, what is left in a phase, or wants to close a phase. - 90plan-phase
Plan the next unplanned phase in a task. Reads state.json to find the next not_started phase, then invokes Explorer to create a detailed implementation plan. Use when you need to create or revise a phase plan. Triggers on: '/plan-phase', 'plan the next phase', 'plan phase',… - 100implement-phase
Execute a single phase from an implementation plan with all quality gates. This skill is the unit of work for implement-plan, handling implementation, verification, code review, ADR compliance, and plan synchronization for ONE phase. Triggers when implement-plan delegates a… - 100doc-driven-implementer-v1
Use only when the user explicitly asks to use doc-driven-implementer. Implements an existing IMPLEMENT.md plan phase by phase with completion gates, test evidence, and doc/handoff synchronization.