Describe

Define what "done" looks like before writing code. Produces a structured test case spec that makes implementation and review unambiguous.

Default path for action-oriented requests:

draft-spec -> review-spec -> implement-from-spec -> commit-after-spec

Do not make the user manually repaste packets just to get the fresh review or implementation branch. Carry the accepted packet forward yourself unless the runtime boundary forces an explicit handoff prompt.

Lifecycle position:

• domain-planner = full feature slices (6 plan files, multi-phase)
• describe = patches, bug fixes, small features (single test spec)
• reproduce = verify the fix after implementation

Execution Profiles