Product Planning

What it does

The /plan-product command creates foundational product documentation through an interactive conversation. It generates three files in agent-os/product/:

• mission.md — Product vision, target users, core problems solved
• roadmap.md — Phased development plan with prioritized features
• tech-stack.md — Technical stack choices for this project

When to run it

• Setting up a new project
• When you want /shape-spec to have product context
• Onboarding team members who need to understand product vision
• When the project lacks documented product goals

The process

1. Check existing docs

If product files already exist, the command asks whether to replace all, update specific files, or cancel.

2. Gather product vision

For mission.md:

• What problem does this product solve?
• Who is this product for?
• What makes your solution unique?

3. Gather roadmap

For roadmap.md:

• What are the must-have features for launch (MVP)?
• What features are planned for after launch?

4. Establish tech stack

For tech-stack.md:

• If a tech-stack standard exists in your standards, asks if this project uses the same stack
• Otherwise asks you to describe frontend, backend, database, and other technologies

5. Generate files

Creates the three markdown files based on your answers.

Integration with /shape-spec

When you run /shape-spec, it reads agent-os/product/ and uses that context when planning features:

• mission.md helps align features with product goals
• roadmap.md helps prioritize and sequence work
• tech-stack.md ensures technical decisions match the project

Updating product docs

Two ways to update:

• Edit directly — The files are just markdown
• Run /plan-product again — Choose "Update specific files" to regenerate only certain files

Tips

• Brief answers are fine—docs can be expanded later
• Skip sections if not applicable; placeholders will be created
• If you have product docs elsewhere, you can create summaries here that reference them