T

Brummel 7715ab44f3 debug: skill + debugger agent migrated

Second skill migrated using the boss pattern. Purely a discipline
skill (RED-first bug fixing); no AILang-specific contracts.

Vocabulary substitutions:
- AILang → "this project" / "the project"
- "ailang-debugger" / "ailang-bencher" / "ailang-architect"
  → "debugger" / "bencher" / "architect" (ailang- prefix dropped)
- "Boss" → "orchestrator"

AILang-specific bits replaced with profile slots:
- `cargo build` / `cargo test` → `commands.build` / `commands.test`
- `ail emit-ir`, `ail run`, `ail build` → "the project's run command"
  (generic — these were AILang CLI specifics)
- `crates/ail/tests/e2e.rs` hardcoded test path → "the testing
  location idiomatic for this project"
- `design/INDEX.md` → `paths.design_ledger` (optional; if the
  project does not have one configured, that step short-circuits)

Universal substance preserved verbatim:
- Iron Law (3 lines)
- Four phases + Phase 4.5 (the three-failures-means-architecture
  rule)
- Status protocol (DONE / DONE_WITH_CONCERNS / NEEDS_CONTEXT /
  BLOCKED)
- All 7 Common Rationalisations rows
- All 8 Red Flags bullets

Dropped from original:
- "former CLAUDE.md 'Bug fixes — TDD, always' section before the
  2026-05-09 skill-system migration" — AILang history, not
  load-bearing for the discipline
- "for the AILang project at /home/brummel/dev/ailang" — AILang
  identity, replaced with generic "this project"

Cross-refs (post-flatten):
- `../implement/SKILL.md` for the GREEN handoff target
- `agents/debugger.md` from the skill body

2026-05-28 15:54:21 +02:00

boss

flatten: skills directly at repo root, no skills/ subdir

2026-05-28 15:46:25 +02:00

debug

debug: skill + debugger agent migrated

2026-05-28 15:54:21 +02:00

docs

flatten: skills directly at repo root, no skills/ subdir

2026-05-28 15:46:25 +02:00

templates

boss: migration pilot — autonomous orchestrator mode generalised

2026-05-28 15:43:39 +02:00

.gitignore

skeleton: plugin layout + docs, skill/agent migration deferred to iter 1

2026-05-28 14:20:13 +02:00

INSTALL.md

skeleton: plugin layout + docs, skill/agent migration deferred to iter 1

2026-05-28 14:20:13 +02:00

install.sh

flatten: skills directly at repo root, no skills/ subdir

2026-05-28 15:46:25 +02:00

README.md

flatten: skills directly at repo root, no skills/ subdir

2026-05-28 15:46:25 +02:00

uninstall.sh

skeleton: plugin layout + docs, skill/agent migration deferred to iter 1

2026-05-28 14:20:13 +02:00

README.md

skills

A self-contained set of development-cycle skills and agents for Claude Code. Originally distilled from the AILang project's in-tree skills/ directory and generalised so it can carry the same discipline across any project.

The plugin is mechanics: pipeline shape, hard-gates, TDD, RED-first bug fixing, agent-template, working-tree-as-quarantine, status protocol. It does not know your project's paths, build commands, vocabulary, or domain-specific contracts. Those live in a small per-project profile file (.claude/dev-cycle-profile.yml) plus the project's CLAUDE.md.

What's in the box

Eight skills, each with the agents it primarily dispatches:

Skill	Trigger	Output	Mandatory?
`brainstorm`	New cycle starting	spec under the configured spec dir	Hard-gate before plan
`planner`	New iteration within an open cycle	plan under the configured plan dir	Hard-gate before implement
`implement`	Plan exists	code + tests, uncommitted in working tree	Standard iteration path
`audit`	Cycle closing OR baseline drift suspected	drift report + regression report	Mandatory at cycle close
`debug`	Bug observed	RED test in working tree + cause analysis	Mandatory RED-first for any bug
`fieldtest`	Orchestrator-dispatched post-audit, surface-touching cycle	example fixtures + friction spec	Optional
`docwriter`	API surface stable across N cycles	rustdoc / docstring sweep	Optional
`boss`	User types `/boss`	autonomous-orchestrator session — dispatches the other skills until done-state or bounce-back	User-invoked, never auto-dispatched

Vocabulary is configurable. AILang calls a cycle a milestone and a sub-cycle an iteration; your project may call them release and sprint, or epic and story, or whatever fits.

The two-layer split

This repo (the plugin) carries everything that is universal:

Pipeline form: design → plan → execute → review → close
Hard-gates between phases
TDD as an independent inner-loop discipline
RED-first bug fixes
Agent template (frontmatter / Iron Law / standing reading / process / status / output / rationalisations / red flags)
Status protocol: DONE / DONE_WITH_CONCERNS / PARTIAL / BLOCKED / NEEDS_CONTEXT
Working-tree-as-quarantine and only-orchestrator-commits
main HEAD sacrosanct
No nested subagent dispatch (Claude Code platform constraint)
No orphan agents

Your project carries a small profile that fills the slots:

Paths: spec dir, plan dir, design ledger, code roots, bench dir
Commands: build, test, lint, regression scripts
Vocabulary: cycle name, sub-cycle name, ledger-entry name
Naming: counter prefix vs date prefix vs flat, slug shape
Standing reading list: concrete files, per role
Git: issue tracker kind, close marker, main-protection policy
Pipeline customisations: which phases are mandatory, when optional ones fire

See docs/profile-schema.md for the full schema and templates/project-profile.yml for a copy-and-fill starting point.

Install

See INSTALL.md. In short: clone, run install.sh, then drop a dev-cycle-profile.yml into each project that should use the plugin.

Status

Migration from AILang's in-tree ~/dev/ailang/skills/ is in progress. The boss skill is the landed pilot; the remaining seven skills follow. See docs/migration.md for the per-skill and per-agent migration checklists and the expected final layout.