enhance(spec-grill): route natural-language intent instead of requiring mode arguments

[sungjunlee]

Summary

Replace the argument-first spec-grill invocation contract with an intent router. Users should not need to memorize modes like map, fill, or audit; those can remain accepted power-user aliases, but the primary workflow should be natural-language routing.

Proposed Behavior

• No argument or ambiguous request -> emit a Grill Report, no edits.
• Candidate discovery language -> emit a Candidate Boundary Report, no edits.
• Missing capability language -> propose the next missing capability, then ask for confirmation before editing.
• Specific capability language -> resolve the mentioned capability or candidate and deep-review it, no edits by default.
• Overlap, stale, or weak-predicate language -> emit a Capability Audit Report, no edits.

Acceptance Criteria

• skills/spec-grill/SKILL.md has an Intent Router section instead of an argument-first Invocation section.
• The skill explicitly says users do not need to memorize arguments.
• Power-user aliases such as map, fill, audit, and exact capability slugs are documented as optional shorthand only.
• Ambiguous requests are report-only by default.
• Editing requires clear edit intent or explicit confirmation.

Notes

Part of #176.

[coderabbitai]

🔗 Related PRs

#160 - [codex] split spec charter and grill skills [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!