specify

Topics in the source

• Specify Workflow
• Steps
• Step 1: Understand the problem
• Step 2: Identify affected systems
• Step 3: Explain impact
• Step 4: Propose options
• Step 5: Recommend next step
• Abbreviation

CANARY: specify-loaded-2026-06-01-7f9501625b833979 Owns sections 1–4 of status/specification.md: problem statement, affected systems, options, recommendation. Creates the file if it does not exist; appends/updates these sections if it does. Per-task scratch goes in tmp/ (not committed); never in status/. Clarify what is actually being asked. Separate symptoms from root causes. When the work started in the explore-idea skill, take its decisions log as input: each agreed decision is a constraint here, not a question to reopen. Cite the I-N ids from status/ideas.md the spec covers in section 1. What is happening? — Observable behavior, errors, or gaps What should be happening? — Expected behavior or desired outcome Since when? — Timeline, triggers, or recent changes that may be related Who is affected? — End users, internal teams, other services, clients What is the urgency? — Blocking production, degrading performance, or planned improvement? Output: a clear, one-paragraph problem statement. Then list success criteria (measurable): each a metric and threshold where one exists (p95latencyms -spec-v - -reader.html and …-annotated.md beside it, and prints both paths; commit them. Load c

This is an excerpt. Refer to the complete source and its current requirements.