implementation-planning

Generate prioritized action items with unique IDs from specification gaps.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/wtah/spec-master --skill implementation-planning-wtah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementation-planning
Source: https://github.com/wtah/spec-master/tree/main/.claude/skills/implementation-planning
Command: npx skills add https://github.com/wtah/spec-master --skill implementation-planning-wtah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to compare specifications with actual implementation and generate concise, auditable action items that guide development at component, container, and infrastructure levels.

Core Features & Use Cases

  • Gap analysis: identify mismatches between specs and current code/tests.
  • Action item generation: create traceable tasks with identifiers, priorities, and direct spec references.
  • Progress planning: produce an ordered, status-aware plan that supports phased delivery across components and containers.
  • Use Case: As a planner, you convert design specs into a concrete plan to hand to development teams for execution.

Quick Start

  1. Gather the {container}/{component} specs and the current implementation snapshot.
  2. Run the planning process to produce .implementation-plan.md.
  3. Review and assign priorities, then start phased work.

Frequently Asked Questions about implementation-planning

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

FAQPage Schema
How do I turn software specifications into an actionable implementation plan?

To turn specifications into an implementation plan, you compare your design specs against the current implementation to identify gaps, then generate a structured plan with prioritized, traceable action items for phased delivery.

What is gap analysis in software implementation planning?

Gap analysis in implementation planning is the process of identifying mismatches between your project specifications and the actual code or tests, which generates traceable action items to resolve those discrepancies.

How do I generate an implementation plan with traceable action items for containers and components?

You generate an implementation plan with traceable action items by running the planning process against your container and component specs, producing a structured .implementation-plan.md file with unique IDs and priorities.

Can I use gap analysis for phased delivery planning across infrastructure and components?

Yes, gap analysis supports phased delivery by producing an ordered, status-aware plan that covers component, container, and infrastructure levels, ensuring development teams follow a structured execution sequence.

What is the best way to track action items generated from specification gaps?

The best way to track action items from specification gaps is to assign unique identifiers and priorities with direct spec references, outputting an auditable .implementation-plan.md file for status tracking.

Do I need current implementation snapshots to generate an actionable implementation plan?

Yes, you need the current implementation snapshot alongside your container and component specs to accurately identify gaps and generate a concrete implementation plan to hand to development teams.