implementationlisted

Implement a feature based on a plan file. Use when: implementing a plan, execute a plan, build from plan, start working on plan, implement PLAN.md. Reads the plan, asks clarifying questions, creates TASKS.md with subtasks in the same folder, then implements each task and marks it done.
tranviet0710/agent-skills · ★ 0 · AI & Automation · score 56

Install: claude install-skill tranviet0710/agent-skills

# Implement From Plan ## When to Use Invoke this skill when the user says: - "implement based on the plan" - "execute the plan" - "build from PLAN.md" - "start working on [feature] plan" - "implement [folder]/PLAN.md" ## Procedure ### Step 1 — Locate & Review the Plan 1. Find the `PLAN.md` (or any `*PLAN*.md`) in the referenced folder or the currently open file. 2. Read the entire plan carefully. 3. Note: the plan's folder is the **working directory** for this skill — all output files go there. ### Step 2 — Ask Clarifying Questions Before doing anything else: - List every ambiguity, assumption, or missing detail you found while reading the plan. - Present them as a numbered question list to the user. - If the plan is fully clear with zero ambiguities, explicitly state: "The plan is clear — no questions. Proceeding to create TASKS.md." - **Wait for the user's answers before continuing.** ### Step 3 — Create TASKS.md Create a `TASKS.md` file **in the same folder as the plan file**, structured as follows: ```markdown # Tasks > Auto-generated from [PLAN.md](./PLAN.md) on <date> ## Task List - [ ] **Task 1 — <short title>** - Description: <what needs to be done and why> - Subtasks: - [ ] <subtask a> - [ ] <subtask b> - [ ] **Task 2 — <short title>** - Description: ... - Subtasks: - [ ] ... ... ``` Rules for task decomposition: - Each task maps to one logical, independently testable unit of work. - Subtasks are concrete, atomic steps (a single fi