 Brummel
|
22653e410a
|
implement: skill + 5 agents migrated — migration complete
Eighth and final skill via the boss pattern. implement carries
the per-task loop mechanics; implementer + spec-reviewer +
quality-reviewer + tester are phase references the
implement-orchestrator inhales at each role-switch.
All eight skills + their agents now live in the plugin. AILang
can switch over by dropping a project profile + removing its
in-tree skills/ in a follow-up.
Vocabulary substitutions:
- AILang → "this project"
- milestone → cycle
- Boss → orchestrator (consistently)
- ailang-implement-orchestrator → implement-orchestrator
- ailang-implementer → implementer
- ailang-spec-reviewer → spec-reviewer
- ailang-quality-reviewer → quality-reviewer
- ailang-tester → tester
AILang-specific bits dropped or generalized:
- `docs/plans/<iteration>.md` / `docs/specs/<milestone>.md`
→ `paths.plan_dir` / `paths.spec_dir`
- `/tmp/ail-iter/<iter_id>/` → `/tmp/iter-<iter_id>/`
- `bench/orchestrator-stats/` → `/tmp/iter-<iter_id>/stats.json`
with note that a project-configured stats dir can be used
- `cargo build --workspace` / `cargo test --workspace` →
`commands.build` / `commands.test`
- `examples/<name>.ail.json` → "fixture in the project's
canonical fixture form"
- `crates/ail/tests/e2e.rs` → "the project's E2E test
location"
- The entire AILang "Architecture rules (binding)" block in
implementer (determinism via BLAKE3, LLVM text IR, schema
ailang/v0, RC + bump allocator, Type::Fn effects,
Implicit-mode rule) → generic "the binding architectural
rules are declared in CLAUDE.md and the design ledger"
- `git log --all --grep='or.2'` reference in
implement-orchestrator → dropped (was AILang project
history)
- `bench/orchestrator-stats/<YYYY-MM-DD>-iter-<iter_id>.json`
→ generic stats path with project-configured option
- AILang-specific quality-bar examples (Implicit-mode RC
unflagged, libllvm call, schema break without migration
note) → generic "anything that violates a binding
architectural rule from CLAUDE.md / design ledger"
- AILang-specific tester examples (`(show 42)` Int dispatch,
ailang/v0 schema) → generic "feature X variant" / "API
response" / observable-behaviour framing
- `Brummel` references → dropped
- `notify.sh` hardcoded → "the project's configured
notification command"
- `iter/...` branches (legacy AILang concept) → "iteration
branches are not used"
Universal substance preserved verbatim across all six files:
- implement SKILL Iron Law (7 lines including new-cycle
triggers and BLOCKED.md convention)
- Per-task sub-status table (9 rows)
- implement-orchestrator: 7-phase process (Phase 0 clean
tree, Phase 1 context load mode-dependent, Phase 2 per-task
loop with 4 sub-phases, Phase 3 E2E, Phase 4 BLOCKED.md,
Phase 5 stats, Phase 6 end-report)
- implement-orchestrator: BLOCKED.md template,
stats.json schema, end-report fixed structure
- implementer: TDD-first discipline, RED-first exceptions,
6-step process, 4-state status protocol
- spec-reviewer: missing/unrequested-extra definitions,
7-step process, 4-state status protocol
- quality-reviewer: 8 quality-bar categories, severity
definitions, 6-step process incl. Strengths-first rule
- tester: 4-clause Iron Law, "named property" doctrine,
4-state status protocol
Common Rationalisations + Red Flags tables preserved across
all six files with vocabulary substitution only. No
discipline compressed.
All seven sibling skills (boss, brainstorm, planner, debug,
audit, fieldtest, docwriter) and the AILang reference
agents now resolve correctly via `../<skill>/...` relative
paths post-flatten.
|
2026-05-28 16:15:10 +02:00 |
|