epic(spec): natural-language routed capability workflow

[sungjunlee]

Summary

Improve the spec-series workflow so users can move from spec-charter to spec-system-map to spec-grill without memorizing argument modes. spec-grill should default to report-only diagnosis, interpret natural-language requests, and only edit capability contracts after an explicit editing intent or confirmation.

Why

The current split between spec-charter, spec-system-map, and spec-grill is structurally good, but the spec-grill workflow still leans too much on argument-style operation. The desired UX is intent-driven: users should be able to say what they want in plain language, and the skill should route safely.

Work Items

• enhance(spec-grill): route natural-language intent instead of requiring mode arguments #177
• enhance(spec-grill): make Grill Report the default diagnostic output #178
• enhance(spec-system-map): add candidate capability boundaries handoff #179
• enhance(spec-grill): expand extract-signals into evidence-grouped collector #180
• docs(spec-charter): recommend concrete next steps without argument memorization #181

Out of Scope

• Fully automatic semantic capability inference
• Auto-writing spec/capabilities.md from extract-signals.js
• New spec-reassess or spec-learn command surface
• Per-capability file split under spec/components/

[coderabbitai]

🔗 Related PRs

#100 - docs: spec-system v0.1 design (layered spec architecture) [merged]
#117 - docs(backlog-charter): note extract-signals clusters by code, not by capability [merged]
#155 - Align spec-system harness signals [merged]
#160 - [codex] split spec charter and grill skills [merged]
#174 - feat(backlog-triage): add spec-aware Decision Review [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!

[sungjunlee]

Completed by PR #182. The spec-series workflow now routes charter -> system map -> report-first capability grill, with natural-language intent routing and evidence-grouped candidate extraction.