plan-feature

Analyze codebases to generate implementation plans and specs documents.

45|3|Updated Jul 10, 2023

Search Tags:#planning #architecture #codebase #feature #specs #planning-workflow

Ready to run

npx skills add https://github.com/incubateur-ademe/benefriches --skill plan-feature

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-feature
Source: https://github.com/incubateur-ademe/benefriches/tree/main/.claude/skills/plan-feature
Command: npx skills add https://github.com/incubateur-ademe/benefriches --skill plan-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create structured, implementation-ready plans for new features by thoroughly analyzing the codebase and architecture patterns.

Core Features & Use Cases

Structured planning: Define scope (API-only, Web-only, Full-stack, Shared) and identify required components.
Codebase-driven analysis: Inspect relevant modules and patterns to inform the plan.
Spec generation: Produce a specs file in specs/<current-timestamp>-<feature-name>.md detailing tasks, milestones, and success criteria.

Quick Start

Run the plan-feature workflow to generate a plan file for your feature. The tool will create specs/<timestamp>-<feature-name>.md and outline the execution steps.

Frequently Asked Questions about plan-feature

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

FAQPage Schema

How do I create an implementation plan for a new feature by analyzing an existing codebase?▼

To create an implementation plan for a new feature, analyze your codebase and architecture patterns to define the project scope, identify required components, and generate a structured specs document detailing tasks and milestones.

What is the best way to write a feature specs document for a full-stack project?▼

Writing a feature specs document for a full-stack project involves inspecting relevant modules to define scope, identifying required API and Web components, and outputting a timestamped markdown file with tasks, milestones, and success criteria.

How do I structure a planning workflow for API and Web feature development?▼

Structure a planning workflow for API and Web feature development by defining the exact scope, inspecting current architecture patterns, and generating a specs file that outlines the necessary inputs, execution steps, and path to completion.

Can I generate a timestamped specs file for feature planning automatically?▼

Yes, you can generate a timestamped specs file for feature planning automatically by running a structured workflow that analyzes your architecture and outputs a markdown document at specs/<current-timestamp>-<feature-name>.md.

Does codebase-driven planning work for both API-only and Web-only scopes?▼

Codebase-driven planning works for API-only, Web-only, Full-stack, and Shared scopes by inspecting relevant modules and patterns to inform the required components and execution path for that specific project boundary.