executing-plans

Load spec, design, and tasks to execute feature plans sequentially.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/nicolaei/claude-plugins --skill executing-plans-nicolaei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/nicolaei/claude-plugins/tree/main/feature-planner/skills/executing-plans
Command: npx skills add https://github.com/nicolaei/claude-plugins --skill executing-plans-nicolaei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end execution of feature plans by loading context from spec, design, and tasks, enabling structured, repeatable implementations.

Core Features & Use Cases

  • Load a plan and read its spec.md, design.md, and tasks.md to understand requirements.
  • Execute tasks in sequence, updating progress markers and handling blockers until completion.
  • Resume work across sessions and align implementation with the planned feature.

Quick Start

Load a plan and start executing tasks in order.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
How do I automate feature plan execution and track task progress?

Automating feature plan execution works by loading your spec.md, design.md, and tasks.md files to sequentially execute tasks, update progress markers, and handle blockers through a guided workflow.

What is the best way to execute planned features sequentially across sessions?

Executing planned features sequentially across sessions is handled by loading contextual documents, executing tasks in order, and resuming work while aligning implementation with the original plan.

Can I resume task workflows and handle blockers if I stop mid-implementation?

Yes, you can resume task workflows across sessions. The workflow loads existing context from your planning documents, updates progress markers, and provides robust blocker handling until feature completion.

Do I need spec, design, and tasks documents to use guided task workflows?

Yes, guided task workflows require spec.md, design.md, and tasks.md documents to load context, understand requirements, and execute planned features sequentially with accurate progress tracking.

How does progress tracking work when implementing planned features?

Progress tracking works by updating progress markers within your tasks.md file as tasks are executed sequentially, ensuring structured implementation and clear visibility into remaining work and blockers.