Planning Features

Break down a PRD or describe your initial feature set.

After initializing your project, define what it can do.

From a PRD

Paste or link to your PRD (product requirements document) and ask:

Break down this PRD into features

The agent will identify features and create a feature tree.

From a description

Describe what you're building:

This is an e-commerce app. Users can browse products,
add items to a cart, and checkout with Stripe.

The agent will identify features like:

Product Catalog
Shopping Cart
Stripe Checkout

Add individual features

For a single feature:

Add a feature for OAuth login

For related features:

Plan features for user authentication: password login, OAuth, and password reset

Claude Code slash command /manifest:plan

Use /manifest:plan for an interactive planning session. The agent will guide you through feature decomposition and confirm before creating.

Review the tree

Ask to see what you have:

Show me the feature tree

The agent will display:

MyProject
├── ◇ Authentication
│   ├── ◇ Password Login
│   ├── ◇ OAuth
│   └── ◇ Password Reset
├── ◇ Product Catalog
├── ◇ Shopping Cart
└── ◇ Stripe Checkout

Legend: ◇ proposed  ○ in_progress  ● implemented  ✗ deprecated

Claude Code slash command /manifest:tree

Use /manifest:tree to quickly display the feature hierarchy with status symbols.

Organize with hierarchy

Group related features under parents:

Move OAuth under Authentication

Or create a parent for existing features:

Group Product Catalog, Shopping Cart, and Checkout under a Storefront parent

Parent features can include context that flows to children: architectural decisions, shared conventions, or technical constraints that apply to all features in that group.

Next step

Continue to Implementing features.