Author Plans
In brief: Author Plans creates or updates markdown stories and scenarios in
plans/so releases and SmartTests stay traced to requirements.
When to use
Use when you need requirements (stories/scenarios) authored or updated before or alongside automation—standalone or as a subflow of Run QA / Upkeep. For quality review of existing plans, use Run requirement quality checks.
Prompt
/testchimp author plans
/testchimp author plans for checkout redesign
/testchimp author plans for US-118
/testchimp scope out US-212
/testchimp author requirements for password reset
/testchimp author story for <objective>
Synonyms: author requirements, author story, author scenarios, scope out.
Scope
Optional. No scope → feature-branch changes, or on the default branch changes since the last author-plans run (else ask). Or name an objective / area in the prompt. Naming an existing US-<n> / TS-<n> scopes write-up of that file (no meta plan gate). scope out US-<n> is the same scoped write-up path when detailing an existing requirement from the Plans viewer.
Policy
Optional author-plans.policy.md for templates, folder conventions, and quality bars. Fallbacks follow policy resolution.
What it does
Authors or updates markdown under plans/ with TestChimp identity-backed entities so coverage, releases, and SmartTest scenario annotation links stay coherent. See Requirement planning.
- Gap / new artifacts: Plan → approve → Execute — the plan lists proposed stories/scenarios (titles/paths); entities are created only after approval.
- Named ordinal (
US-<n>/TS-<n>): skip the meta plan and write up that existing file — clarify with the user and ground the content in repo context.