[codex] split spec charter and grill skills

AGENTS.md

@@ -6,6 +6,14 @@ GitHub Issues + local sprint execution files for Claude Code / Codex.
 
 ```
 skills/
+  spec-charter/
+    SKILL.md               ← CHARTER.md create/amend + reassess contract
+    references/            ← Detailed specs (on-demand)
+    scripts/               ← Deterministic helpers (node)
+  spec-grill/
+    SKILL.md               ← spec/capabilities.md grill contract
+    references/            ← Detailed specs (on-demand)
+    scripts/               ← Deterministic helpers (node)
   dev-backlog/
     SKILL.md               ← Core process (~194 lines)
     references/            ← Detailed specs (on-demand)

CHANGELOG.md

@@ -6,7 +6,9 @@ Each entry links the GitHub issue (the canonical spec) and the merge PR (the shi
 
 ## [Unreleased]
 
-Nothing yet.
+### Changed
+
+- Split the old `backlog-charter` surface into the spec-series skills `spec-charter` and `spec-grill`. `spec-charter` owns `CHARTER.md` create/amend/reassess; `spec-grill` owns `spec/capabilities.md` capability-contract authoring. Closes [#157](https://github.com/sungjunlee/dev-backlog/issues/157), [#158](https://github.com/sungjunlee/dev-backlog/issues/158), and [#159](https://github.com/sungjunlee/dev-backlog/issues/159).
 
 ## [0.5.0] — 2026-05-22
 

CHARTER.md

@@ -15,8 +15,9 @@ sessions is rebuilt from scratch each time.
 ## Approach           <!-- Tier 1 · Direction (human-gated) -->
 Keep GitHub Issues as the canonical task spec; add a thin, explicit,
 markdown-only execution hub (the active sprint file) that humans and agents
-both read and update. Companion skills (`backlog-triage`, `backlog-charter`)
-groom and orient the same GitHub-anchored state — they never replace it.
+both read and update. Companion skills (`backlog-triage`, `spec-charter`,
+`spec-grill`) groom and orient the same GitHub-anchored state — they never
+replace it.
 No server, no daemon, no hidden state, no silent sync.
 
 ## Non-Goals          <!-- Tier 1 · Direction (human-gated) -->
@@ -43,3 +44,4 @@ No server, no daemon, no hidden state, no silent sync.
 | 2026-05-22 | `CHARTER.md` is a separate file at repo root, not merged into `_context.md`           | The axis must stay a <5-min-read yardstick; `_context.md`'s HOW-knowledge would dilute it        | —          |
 | 2026-05-22 | The Alignment Check is prompt-driven inside `backlog-triage`, not a new `triage-*.js` | Issue→objective mapping is semantic, unlike the deterministic relate/stale scripts               | —          |
 | 2026-05-22 | Patterns from Fractal and gsd-2 are absorbed, not integrated                          | Both own the whole project lifecycle and conflict with the GitHub-Issues-anchored model          | —          |
+| 2026-05-29 | `backlog-charter` splits into `spec-charter` and `spec-grill`                         | Existing-repo onboarding needs a discoverable second step from project charter to capability contracts | 2026-05-22 |

CLAUDE.md

@@ -8,10 +8,15 @@ GitHub Issues + local sprint execution files for Claude Code / Codex.
 
 ```text
 skills/
-  backlog-charter/
-    SKILL.md               ← CHARTER.md create/amend contract
-    references/            ← Amendment + alignment specs
+  spec-charter/
+    SKILL.md               ← CHARTER.md create/amend + reassess contract
+    references/            ← Amendment, alignment, objective, reassess specs
     templates/             ← Runtime CHARTER.md template
+  spec-grill/
+    SKILL.md               ← spec/capabilities.md grill contract
+    references/            ← Capability heuristics + spec-system research
+    scripts/               ← Brownfield signal extraction helper
+    templates/             ← Runtime capabilities template
   backlog-triage/
     SKILL.md               ← Open-issue grooming contract
     references/            ← Detailed specs (on-demand)

README.md

@@ -94,6 +94,15 @@ Then use the skill during your coding session:
 /dev-backlog sync
 ```
 
+Optional spec-series setup:
+
+```text
+/spec-charter create
+/spec-grill
+```
+
+`spec-charter` creates the project-wide `CHARTER.md` axis. On existing repos, follow it with `spec-grill` to author `spec/capabilities.md`, the middle layer of capability contracts and Hard Constraints.
+
 For the detailed sprint contract, section semantics, and full script inventory, see [skills/dev-backlog/SKILL.md](skills/dev-backlog/SKILL.md).
 
 Important if you use `dev-relay`: sprint files are not fully freeform markdown.

skills/backlog-triage/SKILL.md

@@ -4,7 +4,7 @@ argument-hint: "[collect|relate|stale|report|apply] [options]"
 description: Interactive backlog grooming for open GitHub Issues. Classifies, relates, flags stale/obsolete, and proposes priorities — produces a markdown triage report you review before applying. Advisory by default; mutations require explicit --apply. Use for backlog review, issue grooming, stale cleanup, priority re-ranking, 백로그 정리, 이슈 검토, 트리아지, 정리.
 compatibility: Requires gh CLI and git. Works on Claude Code and Codex.
 metadata:
-  related-skills: "backlog-charter, dev-backlog, relay, relay-plan"
+  related-skills: "spec-charter, dev-backlog, relay, relay-plan"
 ---
 
 # Backlog Triage
@@ -32,7 +32,7 @@ Sibling skill to dev-backlog, not a replacement. dev-backlog is the execution hu
 
 Every script in this phase is read-only. Running any number of times is safe. The snapshot is the canonical artifact; all downstream analysis consumes it via `--snapshot PATH` (no re-fetch).
 
-Alignment Check is prompt-driven, not a `triage-*.js` script: when `CHARTER.md` exists, map open issues to Objectives using `../backlog-charter/references/alignment.md` and emit an `## Alignment` report section. When `CHARTER.md` is absent, skip this step entirely and keep the existing report shape.
+Alignment Check is prompt-driven, not a `triage-*.js` script: when `CHARTER.md` exists, map open issues to Objectives using `../spec-charter/references/alignment.md` and emit an `## Alignment` report section. When `CHARTER.md` is absent, skip this step entirely and keep the existing report shape.
 
 ### Phase 2 — Apply (opt-in, explicit)
 
@@ -129,7 +129,7 @@ Active Objectives with no open issue advancing them (medium severity).
 Issues that violate a Non-Goal (high severity).
 
 ### Proposed CHARTER changes
-Seed proposals for `backlog-charter` amend; triage does not mutate `CHARTER.md`.
+Seed proposals for `spec-charter` amend; triage does not mutate `CHARTER.md`.
 
 ## Apply Checklist
 Consolidated list of every anchored action for scan-and-check review. The apply step parses
@@ -147,7 +147,7 @@ source sections above both count as acceptance surfaces (see `references/apply.m
 | Milestone lifecycle, monthly progress issue | dev-backlog |
 | AC checkboxes inside issue bodies (`AC:BEGIN`/`END`) | dev-backlog |
 | Open-issue classification, relationships, stale flags | backlog-triage |
-| CHARTER alignment of open issues | backlog-triage (report; `CHARTER.md` mutations stay with `backlog-charter`) |
+| CHARTER alignment of open issues | backlog-triage (report; `CHARTER.md` mutations stay with `spec-charter`) |
 | Priority / milestone **proposals** | backlog-triage (report) |
 | Priority / milestone **mutations** | backlog-triage (`--apply`) |
 | Post-triage sprint planning | dev-backlog (reads report, edits sprint file) |
@@ -158,7 +158,7 @@ Recommended cadence: run backlog-triage weekly or bi-weekly. Feed the report's M
 
 ## Process
 
-**Collect → Analyze → Report.** One `gh` fetch, one snapshot, downstream scripts consume it via `--snapshot`. Re-fetching in each script is a bug — it creates drift across signals. During Analyze, run the prompt-driven Alignment Check when `CHARTER.md` is present; its Proposed CHARTER changes feed `backlog-charter` amend and are not applied by `triage-apply.js`, which only mutates GitHub issues.
+**Collect → Analyze → Report.** One `gh` fetch, one snapshot, downstream scripts consume it via `--snapshot`. Re-fetching in each script is a bug — it creates drift across signals. During Analyze, run the prompt-driven Alignment Check when `CHARTER.md` is present; its Proposed CHARTER changes feed `spec-charter` amend and are not applied by `triage-apply.js`, which only mutates GitHub issues.
 
 **Review the report.** Read each proposal. Check the ones you accept (flip `[ ]` → `[x]`). Leave rejected ones unchecked. Do not delete anchor comments; unchecked anchors are ignored by apply.
 
@@ -193,7 +193,7 @@ Flags on individual scripts override config.
 - `references/relationships.md` — mention / blocks / depends-on / duplicate heuristics, evidence format
 - `references/stale.md` — obsolescence signals, thresholds, suggested-action grammar
 - `references/apply.md` — anchor grammar, parse rules, idempotency contract, apply-log schema
-- `../backlog-charter/references/alignment.md` — prompt-driven CHARTER work↔objective mapping and drift severity rules
+- `../spec-charter/references/alignment.md` — prompt-driven CHARTER work↔objective mapping and drift severity rules
 
 ---
 

skills/dev-backlog/SKILL.md

@@ -4,14 +4,14 @@ argument-hint: "[orient|plan|work|next|sync] [issue-number]"
 description: Manage development work through GitHub Issues + local sprint files. Issues/Milestones are the source of truth; local sprint files handle execution — batching, ordering, context, and progress. Use for creating issues, planning sprints, checking what to work on, reviewing progress, syncing with GitHub, managing milestones, backlog, 다음 작업, 이슈 만들어, 스프린트 계획, 백로그.
 compatibility: Requires gh CLI and git. Works on Claude Code and Codex.
 metadata:
-  related-skills: "backlog-charter, backlog-triage, relay, relay-plan, relay-dispatch, relay-review, relay-merge"
+  related-skills: "spec-charter, spec-grill, backlog-triage, relay, relay-plan, relay-dispatch, relay-review, relay-merge"
 ---
 
 # Dev Backlog
 
 README covers install and human quick start. This skill file is the execution contract for agents: file roles, sprint structure, process, and script behavior.
 
-Related skills: [`backlog-charter`](../backlog-charter/SKILL.md) for the optional `CHARTER.md` reference axis, and [`backlog-triage`](../backlog-triage/SKILL.md) for weekly backlog grooming before you plan the next sprint.
+Related skills: [`spec-charter`](../spec-charter/SKILL.md) for the optional `CHARTER.md` reference axis, [`spec-grill`](../spec-grill/SKILL.md) for `spec/capabilities.md`, and [`backlog-triage`](../backlog-triage/SKILL.md) for weekly backlog grooming before you plan the next sprint.
 
 Two layers, each with a clear job:
 

skills/dev-backlog/references/integration-contract.md

@@ -37,7 +37,7 @@ Extraction: read lines between the matched `## ` heading and the next `## ` head
 The optional `component:` field is one primary routing handle into `spec/capabilities.md`.
 
 ```yaml
-component: "charter-management"
+component: "spec-charter"
 ```
 
 Rules: