autowork-plan

To generate a PRD and test specs, provide a product request to the planning phase. It produces execution-ready artifacts like context snapshots and plans without writing code, ensuring outputs are concrete and scoped.

The best way to turn workflow requests into execution-ready artifacts is using a plan-only approach. It transforms requests into structured PRDs and test specs, surfaces unknowns, and guides handoff decisions before implementation begins.

Yes, you can create planning artifacts without executing code. It enforces plan-only execution by generating PRDs, plans, and test specs for review, preventing premature implementation while highlighting key unknowns.

Generating context snapshots works by capturing the essential details of a user request into a structured format. This snapshot feeds into the creation of PRDs and test specs, ensuring all artifacts are testable and scoped.

Yes, it suggests handoff points for autowork execution. After generating execution-ready artifacts like PRDs and test specs, it provides guided prompts and handoff decisions to transition smoothly into the implementation phase.

Your planning workflow needs guardrails to ensure artifacts remain concrete, testable, and scoped. By surfacing key unknowns and enforcing plan-only execution, it prevents scope creep and prepares structured handoff decisions.