implement

Execute plan phases from PLAN.md and write code into spaces/.

69|7|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/TaylorHuston/local-life-manager --skill implement-taylorhuston
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/TaylorHuston/local-life-manager/tree/main/.claude/skills/implement
Command: npx skills add https://github.com/TaylorHuston/local-life-manager --skill implement-taylorhuston

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill executes plan phases by triggering implementation steps and writing code into the designated spaces/ while tracking progress in ideas/ to ensure alignment with the project plan.

Core Features & Use Cases

  • Plan-driven execution: Executes defined phases from PLAN.md and writes code into spaces/ while updating worklog and ideas/.
  • Context-aware implementation: Reads issue context from ideas/ and ensures changes are traced against the plan.
  • Use Case: When you have an issue YB-2 with a PLAN.md, this Skill will execute the next logical phase, commit changes, and record progress in worklog.

Quick Start

/implement yourbench YB-2 1.1 # Execute phase 1.1 of issue YB-2 /implement yourbench YB-2 --next # Auto-find next uncompleted phase /implement coordinatr 003 --full # Execute all remaining phases

Frequently Asked Questions about implement

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

FAQPage Schema
How do I execute specific phases from PLAN.md and write code into spaces?

To execute specific phases from PLAN.md and write code into spaces, use the implement skill to trigger phase steps, generate code, and record progress. It reads issue context from ideas/ to ensure changes align with the project plan.

What is the best way to automate phase advancement during code implementation?

Automating phase advancement during code implementation is handled by the --next command, which auto-finds and executes the next uncompleted phase from PLAN.md. The --full command executes all remaining phases.

How does progress tracking work when implementing a plan phase?

Progress tracking works by updating a worklog and ideas/ directory after executing a phase from PLAN.md. The skill writes code into spaces/ and records progress to ensure changes are traced against the plan.

Do I need a PLAN.md file to automate code writing and phase execution?

Yes, you need a PLAN.md file to automate code writing and phase execution because it serves as the source of phases. The skill also reads issue context from ideas/ to align changes.

Can I run all remaining implementation phases automatically?

You can run all remaining implementation phases automatically by passing the --full flag. This executes every uncompleted phase from PLAN.md sequentially, writes code into spaces/, and updates the worklog.