spec-workflow

## Sibling skills (local only) Sibling CloudBase skills ship beside this skill. Use local relative paths such as `../auth-tool-cloudbase/SKILL.md`. If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do **not** HTTP-fetch remote skill or protocol markdown into the agent context. # Spec Workflow ## Activation Contract ### Use this first when - The request is a new feature, multi-step product change, cross-module integration, or architecture/design task. - Acceptance criteria are unclear and need to be made explicit before implementation. - The work involves multiple files, user flows, database design, or UI design that needs staged confirmation. ### Read before writing code if - You are unsure whether the task should go straight to coding or should first go through requirements, design, and task planning. - The request mentions a new page, a new system, a redesign, a workflow, or a multi-module refactor. ### Then also read - Frontend page or visual design work -> `../ui-design/SKILL.md` - Advanced data-model work -> `../data-model-creation/SKILL.md` ### Do NOT use for - Small bug fixes with clear scope. - One-file documentation updates. - Straightforward config changes. - Tiny refactors where the user already gave exact implementation instructions. ### Common mistakes / gotchas - Jumping into coding before acceptance criteria are explicit. - Skipping user confirmation betwe...