skills.rest
maxenko
maxenkoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan-feature

Plan software features through research, drafting, critique, and finalization workflows.

1|Updated Apr 8, 2026
Search Tags:#workflow#plan#feature-design#engineering-planning#research-agents#plan-draft
One-click install
npx skills add https://github.com/maxenko/claude-skills --skill plan-feature-maxenko
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-feature
Source: https://github.com/maxenko/claude-skills/tree/main/plan-feature
Command: npx skills add https://github.com/maxenko/claude-skills --skill plan-feature-maxenko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning a software feature is error-prone without a repeatable process. This Skill orchestrates a four-phase workflow—research, draft, critique, and finalization—to produce a production-ready plan that teams can execute.

Core Features & Use Cases

  • Four-phase workflow: Research with an agent team, draft a plan, critique with automated agents, and finalize the plan for delivery.
  • Artifact generation: Produces a structured plan document with phased slices, risks, and testing strategies.
  • Repository-aligned outputs: Writes final plan to standard locations and follows project conventions for plan naming and storage.
  • Use Case: When kicking off a new feature, refactor, or architecture decision, run this Skill to generate a concrete, reviewable plan.

Quick Start

Describe the feature you want to plan, and I will generate a draft plan using a four-phase research-to-delivery workflow.

Frequently Asked Questions about plan-feature

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

FAQPage Schema
How do I create a structured feature plan for a new software functionality?▼

This Skill drafts a feature plan by running a four-phase workflow: research, draft, critique, and finalize. It produces a structured plan document with phased work breakdowns, risks, and testing strategies aligned to your repository conventions.

What is the best way to plan software architecture changes and feature redesigns?▼

Planning architecture changes and feature redesigns is best handled through an agent-driven workflow that researches your request, drafts a plan, applies automated critique, and finalizes the output with phased slices and risk coverage.

Can I generate a plan document with risk and testing coverage for my engineering project?▼

Yes, you can generate a plan document that includes risk and testing coverage. The finalization phase outputs structured artifacts containing phased work breakdowns, testing strategies, and frontmatter-driven metadata.

How does the agent-driven critique phase work during feature design?▼

The critique phase uses automated agents to review the drafted feature design. They evaluate the plan for completeness and risks before the finalization phase writes the structured document to standard repository locations.

Do I need specific project conventions to use an automated feature planning workflow?▼

No specific dependencies are required, but the workflow aligns outputs to your project conventions. It follows repository patterns for plan-file generation, naming, storage, and frontmatter-driven metadata.

Related Skills

Explore More Software Engineering Skills→
KrystianYCSilvaKrystianYCSilva

spec-kit-fundamentals

Generates templated clinical documents and automates workflows for faster, error-free reporting.

Community
Intermediate
corbat-techcorbat-tech
1

plan

Generates step-by-step plans for implementing software changes with risk assessment.

Official
Intermediate
scott-rcscott-rc

plan

Slice briefs into phased implementation plans with commit checkpoints.

Community
Advanced
visualityplvisualitypl
4

create_plan

Generate detailed iterative implementation plans from codebase research and user requirements.

Official
Advanced