Test Planning (stably plan)

stably plan

​

Command Syntax

stably plan [prompt...]

​

What It Does

• Reads your codebase and existing tests
• Identifies likely coverage gaps, missing scenarios, and edge cases
• Generates plan files using test.fixme() so the plan is visible in your repo
• Lets you review and refine the plan before turning it into finished tests
• Stays focused on repository analysis rather than browser-driven verification

​

When To Use It

​

Usage

# Analyze the repository and create a broad coverage plan
stably plan

# Focus the plan on a part of the product
stably plan "focus on checkout, login, and billing edge cases"

# Ask for a plan around recent product work
stably plan "look for missing coverage around the new onboarding flow"

​

How It Fits In The Workflow

​

Typical Workflow

# 1. Find gaps
stably plan "focus on checkout and account recovery"

# 2. Review the generated plan files and pick the scenarios you want to implement

# 3. Turn planned coverage into real tests
stably create "implement the highest-priority checkout scenarios from the plan"

# 4. Run the suite
stably test

​

Notes

• stably plan is a repo-analysis command. It does not launch a browser.
• It is intended to produce planning artifacts, not complete end-to-end tests.
• The output is meant to be reviewed by a developer or coding agent before being turned into finished tests.
• The exact files generated depend on what the agent finds in your repository, so review the new test.fixme() plan files after the command completes.