spec-grilllisted

# spec-grill Author `spec/capabilities.md`, the middle layer between `spec/charter.md` and day-to-day execution work. Create the file only when a keep condition holds; amend it if it already exists. Not a file generator from directory names, and not the second step of a required pipeline. ## Execution contract ### Intent router Do not require users to memorize arguments. Interpret the user's request and choose the safest matching route. Power-user aliases such as `map`, `fill`, `audit`, and exact capability slugs are accepted, but they are optional shorthand, not the primary workflow. | User intent | Route | Writes? | |-------------|-------|---------| | No argument, ambiguous capability request, or "look at the capabilities" | **Grill Report** (short diagnostic by default): diagnose current evidence and recommend next action. | No | | "Find capability candidates", "map repo capability boundaries", or `map` | **Candidate Boundary Report**: collect raw candidates and classify them as accepted / rejected / merged / split candidates. | No | | "Add the next missing capability", "fill the missing capability", "write/apply the recommended edit", "write the recommended first capability", "next safest capability 작성해줘", "문서 적을 건 적고 다음 제안해줘", or `fill` | **Next Capability Proposal**: propose exactly one missing capability and ask for confirmation before editing unless the user clearly authorized the edit. | Only after confirmation or clear edit authorization | | Mentions a known ca