planning-implementation

Convert research findings into a phased implementation plan with dependencies and success criteria.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/fascari/ai-config --skill planning-implementation-fascari
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-implementation
Source: https://github.com/fascari/ai-config/tree/main/skills/planning-implementation
Command: npx skills add https://github.com/fascari/ai-config --skill planning-implementation-fascari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates research findings into a detailed, phased, verifiable implementation plan. Does not write code. Produces the plan that implementing-feature will follow.

Core Features & Use Cases

  • Compatibility Analysis before designing phases to surface breaking changes and record decisions
  • Phase design that respects architecture dependency order and ensures testability
  • Plan artefact that can be reviewed and approved before implementation

Quick Start

Provide input briefs and repository context; the skill will generate a structured implementation plan for review.

Frequently Asked Questions about planning-implementation

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

FAQPage Schema
How do I convert research findings into an implementation plan?▼

To convert research findings into an implementation plan, provide your input briefs and repository context. The skill generates a structured, verifiable plan file with phases, dependencies, and success criteria for review.

What is a phased implementation plan with architecture constraints?▼

A phased implementation plan with architecture constraints is a rollout strategy that respects dependency order and ensures testability. It translates feature requests or fixes into structured, verifiable phases before code is written.

How do I analyze compatibility and breaking changes before designing implementation phases?▼

To analyze compatibility and breaking changes before designing phases, the skill performs a dedicated compatibility analysis. It surfaces breaking changes and records decisions to ensure the rollout respects architecture dependency order.

Where is the generated implementation plan artefact stored?▼

The generated implementation plan artefact is stored as a markdown file at .github/plans/{slug}/implementation-plan.md. This structured file includes the designed phases, dependencies, and success criteria for approval.

Does this implementation planning skill write code or only produce the plan?▼

This implementation planning skill does not write code. It strictly produces a verifiable plan artefact that an implementing-feature skill or developer will follow during actual code execution.

What is the best way to manage rollout risk for complex feature requests?▼

The best way to manage rollout risk for complex feature requests is designing a structured plan with verifiable success criteria and compatibility analysis. This approach surfaces breaking changes before implementation begins.