docs(spec-grill): clarify capability-level Decisions seeding

[sungjunlee]

Dogfooding finding (2026-05-23, PR #110; res scoped 2026-05-31).

When writing dev-backlog's own spec/capabilities.md, capability-level Decisions needed a clearer seeding rule. Some charter Decisions were useful inside a capability block; others would have been duplication.

The current question is not whether Decisions exist. It is when a cross-cutting charter Decision should be echoed at capability level, when a capability-only Decision should stay local, and when a capability-level finding should be promoted through spec-charter amend.

Scope

Update skills/spec-grill/references/capabilities.md. Add a short pointer in skills/spec-grill/SKILL.md only if needed.

Proposed rule

• Echo a spec/charter.md Decision at capability level only when the rationale is needed in context to understand a Behavior or Hard Constraint.
• Otherwise, leave the capability Decisions table empty; the cross-cutting record lives in the charter.
• Capability-only Decisions land in the capability block.
• A capability-level Decision that affects more than one capability should be promoted through spec-charter amend; old Decisions rows remain append-only.

Acceptance Criteria

• references/capabilities.md documents the Decisions seeding pattern.
• The rule is explicit about echo vs. leave empty vs. local-only Decision.
• Promotion rule from capability Decisions to spec-charter amend is documented.
• Wording uses current spec-charter / spec-grill names, not retired backlog-charter paths.

[coderabbitai]

🔗 Related PRs

#106 - docs(backlog-charter): create-mode interview + signals + seed-Decisions guidance (#93 #94 #96) [merged]
#110 - docs: dogfood spec/capabilities.md for dev-backlog itself (#105) [merged]
#117 - docs(backlog-charter): note extract-signals clusters by code, not by capability [merged]
#160 - [codex] split spec charter and grill skills [merged]
#174 - feat(backlog-triage): add spec-aware Decision Review [closed]

---

📝 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]

2026-05-31 triage update: scope moved from the retired backlog-charter name to spec-grill. Target doc is skills/spec-grill/references/capabilities.md, with any short pointer in skills/spec-grill/SKILL.md only if needed. Keep the useful rule: echo a charter Decision at capability level only when the rationale is needed to understand a Behavior or Hard Constraint; promote genuinely cross-cutting capability Decisions through spec-charter amend; capability-only Decisions can stay local.