spec-creator

# Spec Creator Turns a fuzzy feature request into spec files a coding agent can implement without guessing. Different from a PRD: the audience is an agent, the currency is technical precision, and each slice is small enough to compile and test on its own. ## Workflow ### 1. Restate the request In one or two sentences, repeat back what you understood. Wait for confirmation. If the user's request is already detailed this is a sanity check; if it's terse ("add biometric unlock") this is where you catch a misread before it propagates. ### 2. Detect the repo Read the top-level `AGENTS.md` / `CLAUDE.md` and skim the folder layout. Note language, frameworks, and any "stable core" or "do not touch" rules. **If the repo is KeeForge** (Swift 6 + SwiftUI + XcodeGen + `project.yml` + `AutoFillExtension`), also read `references/keeforge-overlay.md` and apply it on top of this workflow. ### 3. Clarify, adaptively Pick the 3–6 questions that actually matter for this feature and ask them in one `AskUserQuestion` batch. A question is worth asking when all three are true: the answer changes what gets built, a reasonable person could answer it more than one way, and the agent can't infer it from the repo. Pull from these categories — don't ask all of them, pick what fits: - **Scope.** New feature, enhancement, or fix? What's explicitly out of scope? Phased rollout? - **UX.** Entry point? Happy-path flow? Which states need explicit UI (empty, loading, error, offline)? - **Data.** New p...