implement

Dispatch pending plan phases to TDD-enforced subagent workflows with validation.

19|2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/bjornjee/agent-dashboard --skill implement-bjornjee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/bjornjee/agent-dashboard/tree/main/adapters/claude-code/skills/implement
Command: npx skills add https://github.com/bjornjee/agent-dashboard --skill implement-bjornjee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning an approved multi-phase coding plan into reliable, test-driven work without overloading a single agent session, while ensuring each phase lands exactly one commit and passes the project test gate.

Core Features & Use Cases

  • Multi-phase dispatch with sequential execution: Breaks a plan into ## Phases checklist items and dispatches the next pending ### Phase X: name section to a fresh subagent, enforcing ordering.
  • Strict workflow gates: Verifies make test is green and confirms exactly one new commit landed per phase before marking the phase done.
  • Resumable from plan state: Re-invoking the skill resumes automatically from the first unchecked phase based on the plan file, including partially completed worktrees.
  • Worktree and plan validation: Ensures the skill is run from the correct feature worktree and resolves the approved plan path via .feature-plan-path, with fallback selection if missing.

Quick Start

Run /agent-dashboard:implement from inside your feature worktree after you hand off an approved plan by choosing Hand off to /agent-dashboard:implement in the plan approval probe.

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce TDD and exactly one commit per phase in a multi-phase git workflow?

Multi-phase dispatch enforces TDD by sending each plan phase to a subagent, requiring make test to pass, and verifying exactly one new commit lands before marking the phase done.

Can I resume a test-driven implementation plan from the last completed phase if my session drops?

Yes, resuming a test-driven implementation plan is supported by automatically detecting the first unchecked phase in the plan file, including recovering from partially completed git worktrees.

How does phase dispatch work with git worktrees and tmux agents?

Phase dispatch works by sending the next pending phase heading to a fresh subagent within your feature git worktree, ensuring sequential execution and strict workflow validation.

What format does my plan file need to follow for automatic phase dispatch to work?

Your plan file needs an explicit ## Phases checklist with corresponding ### Phase headings, and the worktree must resolve the approved plan path via a .feature-plan-path file.

Do I need to run make test manually before committing each phase of my feature plan?

No, the workflow gate automatically verifies make test is green and confirms exactly one new commit landed per phase before flipping the checklist item to done.

What happens if a phase dispatch fails the test gate or produces multiple commits?

If the test gate fails or multiple commits are detected, the phase is not marked complete and the checklist is not flipped, preventing invalid phase dispatch from advancing.