plan

Name: plan
Availability: InStock
Author: stella

Generate standardized feature plan files with structured sections in .agents/plans.

163|43|Updated May 3, 2026

Search Tags:#workflow #architecture #documentation #plan #product-management #feature-planning #planning-guidelines

Ready to run

npx skills add https://github.com/stella/stella --skill plan-stella

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/stella/stella/tree/main/.agents/skills/plan
Command: npx skills add https://github.com/stella/stella --skill plan-stella

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and document upcoming feature work by generating a standardized plan file in the repository.

Core Features & Use Cases

Sequential plan generation: creates a next-plan file under .agents/plans/ with a unique sequential number.
Context-driven planning: reads existing architecture notes and goals to guide the plan.
Structured plan template: includes sections such as Goal, Design Decisions, Scope, Implementation, Test Cases, and Open Questions.
Guidelines and review flow: prompts for confirmation with the user before saving to enforce quality and alignment.

Quick Start

Provide a feature slug and context, and the skill will create the next sequential plan file in .agents/plans/.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I create a standardized feature plan file in my repository?▼

To create a standardized feature plan, provide a feature slug and context. The skill reads existing architecture notes and goals, then generates a structured plan file with sections for Goal, Design Decisions, Scope, Implementation, Test Cases, and Open Questions, saving it sequentially to .agents/plans/.

What sections should a feature planning document include for architecture reviews?▼

A feature planning document for architecture reviews should include structured sections for Goal, Design Decisions, Scope, Implementation, Test Cases, and Open Questions. This standardized template enforces consistency and aligns product teams during feature ideation and scoping.

How do I document design decisions and scope for upcoming feature work?▼

Document design decisions and scope by generating a plan file that reads existing architecture notes and goals. The skill enforces a structured template with dedicated sections, prompting for user confirmation before saving to ensure quality and alignment with project objectives.

Can I use existing architecture notes to guide feature scoping and task rationalization?▼

Yes, context-driven planning reads existing architecture notes and goals to guide feature scoping and task rationalization. The skill uses this context to generate a sequential plan file, ensuring new feature work aligns with established architecture and product goals before saving.

What is the best way to maintain consistent feature planning files across a product team?▼

The best way to maintain consistent feature planning files is sequential plan generation. The skill creates a next-plan file under .agents/plans/ with a unique sequential number, using a standardized template and a review flow that prompts for confirmation before saving.

Do I need a specific repository structure to generate sequential plan files?▼

Generating sequential plan files requires a .agents/plans/ directory in the repository. The skill saves the structured plan file, featuring Goal, Design Decisions, Scope, Implementation, Test Cases, and Open Questions sections, to this location with a sequential numeral.