Setup

Run once per project during the first orient. Configures the issue tracker.

Bundled skills

The following mattpocock/skills are bundled with this plugin and always available (no external detection needed):

• grilling — core grilling discipline
• grill-with-docs — user-invoked grilling + domain modeling
• domain-modeling — ADR/glossary maintenance
• tdd — TDD reference material
• prototype — throwaway artifact methodology
• codebase-design — shared design vocabulary
• diagnosing-bugs — structured bug diagnosis
• improve-codebase-architecture — visual architecture review

These live in skills/ and are referenced by other skills at defined integration points. No detection scan is needed for them.

Steps

1. Acknowledge bundled skills. State in one line: "8 mattpocock/skills are bundled with this plugin (grilling, domain-modeling, tdd, prototype, codebase-design, diagnosing-bugs, improve-codebase-architecture, grill-with-docs) — available at their integration points automatically."
2. Ask which issue tracker to use — one question, three options:
   • Local files (docs/agents/) — simplest, no account needed, version-controlled. Default if no strong preference.
   • GitHub Issues — if the project has or will have a GitHub remote.
   • Linear — if the user already uses Linear.
3. If GitHub or Linear: confirm which repo/project to use, or whether to create one. If creating: default to private.
4. Create .agent/state.json with the v2 schema:

   {
     "version": 2,
     "status": "orienting",
     "map_ref": "docs/agents/map.md",
     "issue_tracker": "<chosen>",
     "tracker_repo": null,
     "risk_posture": "standard",
     "doc_tier": null
   }

5. Determine the documentation tier using reference/doc-tiers.md. For empty directories, weight heavily on user intent. For existing code, blend heuristic signals with any existing docs (treated as a floor). Update doc_tier in state.json.

What this skill must never do

• Never assume GitHub because a .git remote exists — ask.
• Never skip the tracker question.