From feature-planner
Execute implementation tasks from a feature plan. Reads spec and design for context, works through tasks sequentially with progress tracking. Use when user says "execute", "implement the plan", "start building", "work on tasks", or wants to continue implementation of a planned feature.
npx claudepluginhub nicolaei/claude-plugins --plugin feature-plannerThis skill uses the workspace's default tool permissions.
Execute implementation tasks from a feature plan created by `feature-planner:planning-features`. Reads context from spec and design documents, then works through tasks sequentially - marking progress as you go.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Execute implementation tasks from a feature plan created by feature-planner:planning-features. Reads context from spec and design documents, then works through tasks sequentially - marking progress as you go.
If the user specifies a feature name, use that. Otherwise, run the list-plans script and ask which plan to work on:
./feature-planner/scripts/list-plans.sh
Present the table and ask: "Which feature would you like to work on?"
Read all three documents from .plans.local/features/[feature-name]/:
Note any skills mentioned in the design document - invoke them as needed during implementation.
Work through tasks in order. For each task:
- [ ] → - [~]- [~] → - [x]Continue until blocked, a task fails, or all tasks complete.
If blocked or a task fails:
Track progress in tasks.md using these markers:
| Marker | Meaning |
|---|---|
- [ ] | Pending - not started |
- [~] | In progress - currently working |
- [x] | Complete - finished |
Only one task should be [~] at a time.
Run continuously through tasks until:
If the user requests pair programming style:
User can request this mode by saying "pair with me", "let's pair program", or "pause between tasks".
User: Execute the task-execution plan
Claude: Let me load the plan context...
[Reads spec.md, design.md, tasks.md]
I see 9 tasks across 6 phases. 3 are already complete.
Starting with: "Create scripts/list-plans.sh"
[Marks task [~] in progress]
[Does the work]
[Marks task [x] complete]
Moving to next task: "Create skills/execute/SKILL.md"
...