plan-feature

Generate implementation-ready plans and technical specs for complex changes.

75|6|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/mblode/agent-skills --skill plan-feature-mblode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-feature
Source: https://github.com/mblode/agent-skills/tree/main/skills/plan-feature
Command: npx skills add https://github.com/mblode/agent-skills --skill plan-feature-mblode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates implementation-ready plans and specs for complex changes without writing code. Use when the user asks for a plan/spec/roadmap, requests a detailed plan, or when a change spans multiple files/systems and needs discovery, sequencing, or architecture decisions.

Core Features & Use Cases

  • Plan discovery and requirements capture for multi-file or multi-system changes.
  • Sequenced architecture decisions and risk/constraint analysis.
  • Generate a concrete, implementation-ready plan that can guide downstream work without writing code.

Quick Start

Describe the feature scope and constraints, and I will generate an implementation-ready plan.

Frequently Asked Questions about plan-feature

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

FAQPage Schema
How do I plan complex multi-file architecture changes without writing code?

To plan complex multi-file architecture changes without coding, describe your feature scope and constraints to generate an implementation-ready plan. This process captures discovery requirements, sequences architecture decisions, and aligns documentation with acceptance criteria.

What is feature discovery and sequencing for a technical spec?

Feature discovery and sequencing for a technical spec is the process of capturing requirements, analyzing risks and constraints, and ordering architecture decisions. It ensures complex multi-system changes are documented and aligned with established standards before implementation.

Can I generate a roadmap for multi-system changes using this approach?

Yes, you can generate a roadmap for multi-system changes by providing the feature scope and constraints. The approach produces a concrete, implementation-ready plan that guides downstream work and documents architecture decisions without writing code.

How do I create an implementation-ready plan for a new feature?

You create an implementation-ready plan for a new feature by defining the feature scope and constraints. The system then generates technical specs, sequences architecture decisions, and performs risk analysis to guide downstream development.

Does this approach work for documenting risk and constraint analysis?

Yes, this approach works for documenting risk and constraint analysis by integrating it directly into the generated technical specs. It sequences architecture decisions and ensures documentation alignment with established standards and acceptance criteria for complex changes.