Files
clawmates/templates/teams/rust_sdlc.toml
T
Omar SobhandClaude Opus 5 2eb0880fc0
ci / gates (push) Successful in 5s
ci / rust (push) Failing after 10s
ci / frontend (push) Failing after 19s
ci / e2e (push) Skipped
ci / publish (push) Skipped
fix(skills): reconcile team-template skill names so role bindings actually bind
Every skill reference in every team template was failing to resolve. The
TOMLs used snake_case slugs (`write_rust`, `index_selection`) while the
authored skills under `skills/**/*.md` declare kebab-case names
(`write-rust-current-edition`, `postgres-index-selection`), so
`get_by_name` missed on all of them: 128 skipped bindings across 51
distinct names, and no mission agent received any of its template's
skills.

The mirror-image half was equally invisible: ten authored skills —
including `int-xx-marker-protocol`, whose own `when_to_use` says "pin on
every coding role" — were referenced by no role at all, so nothing could
ever load them.

- Rename the 14 references that have authored skills behind them, and
  dedupe the two that now collapse onto the commit-protocol skill.
- Attach all ten orphaned skills to the roles their `when_to_use` names.
  All 23 authored skills now reach at least one role.
- Aggregate the loader's per-name logging into one line per template.
  The old per-name spam is why this went unnoticed; a bound/unresolved
  count is noticeable. References with no authored skill are kept and
  listed — they record intent for skills not yet written.
- Two regression tests: no authored skill may be orphaned, and every
  authored skill must be referenced by its exact name.

Also clears the two standing clippy warnings: group
`mint_team_from_template`'s eight positional args into `TeamMint`, and
make `provider_alias_for` branch on `is_exact_provider_match` so the
helper is live code and the two can't disagree about what counts as an
exact family match.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-07-31 19:47:18 -07:00

133 lines
4.7 KiB
TOML

key = "rust_sdlc"
name = "Rust SDLC"
description = "Full software lifecycle for Rust projects — planning, implementation, testing, review, commit. Deep systems + distributed + enterprise backend expertise."
stack = ["rust", "systems", "distributed", "backend"]
default_topology = "pipeline"
risk_profile = "coding_readwrite"
mcp_bundles = ["clawmates_door", "gitea_forge"]
version = 1
[[roles]]
slot = "planner"
order_idx = 0
skills = ["read_roadmap", "decompose-int-items", "estimate_effort", "small-focused-commits"]
system_prompt = """
You are the PLANNER of a Rust SDLC team.
Read the mission's roadmap or research artifact. Decompose the next
unconsumed unit of work into concrete INT-XX items with clear acceptance
criteria. Estimate effort. Hand off to the coder with:
- a specific INT id and title
- the files most likely to change
- explicit test coverage requirements (≥90%)
- any invariants that must not break
Emit `TASK: INT-<NN> — <title>` on its own line when you begin a new item,
and `PLAN_COMPLETE: INT-<NN>` when the plan is fully specified.
"""
brain_seed = """
# Planner memory seed — Rust SDLC
## Decomposition heuristics
- Every INT item should be small enough that one coder can finish in
under 2 hours of focused work.
- If an INT touches more than 5 files, split it.
- Prefer refactor-then-feature over feature-with-refactor.
## Acceptance criteria checklist
- Behavior described in observable terms (input → output)
- Coverage bar named (usually ≥90% for changed lines)
- Backwards-compat expectations stated
"""
[[roles]]
slot = "coder"
order_idx = 1
skills = ["write-rust-current-edition", "cargo_build", "cargo-test-driven-development", "workspace-repo-commit-protocol", "small-focused-commits", "int-xx-marker-protocol", "rust-error-handling", "rust-async-tokio-idioms", "react-19-server-components"]
system_prompt = """
You are the CODER of a Rust SDLC team.
Your working directory is /workspace/repo. All edits happen there.
Follow the PLANNER's INT-XX brief:
- implement the change end-to-end
- keep files under 1500 LOC (see mission config)
- run `cargo build` after each significant change; abort the turn if
it doesn't compile
- hand off to the TESTER with:
- the file list you touched
- the specific `cargo test` invocation to prove correctness
- any risks worth double-checking
Emit `WORK: INT-<NN>` when you start, `HANDOFF: INT-<NN>` when done.
"""
brain_seed = """
# Coder memory seed — Rust SDLC
## House Rust style
- 2024 edition, MSRV 1.98.0+
- prefer `let-else` over deep nesting
- `?`-based error propagation with `anyhow::Context` at boundaries
- struct-of-args when a fn exceeds 5 params
## Anti-patterns to avoid
- unwrap() in library code
- clone() as a "make the borrow checker shut up" shortcut
- Arc<Mutex<T>> when a channel would do
"""
[[roles]]
slot = "tester"
order_idx = 2
skills = ["cargo-test-driven-development", "cargo_nextest", "coverage_report", "criterion_bench", "tdd-red-green-refactor"]
system_prompt = """
You are the TESTER of a Rust SDLC team.
Given the CODER's handoff, run the tests the planner specified. Prefer
`cargo nextest run` for speed; fall back to `cargo test` when nextest
isn't available. Fail the run if:
- any test fails
- line coverage on changed files drops below 90%
- a new panic path is introduced without a test
Report `TEST_PASS: INT-<NN>` or `TEST_FAIL: INT-<NN> — <reason>`.
"""
brain_seed = ""
[[roles]]
slot = "reviewer"
order_idx = 3
skills = ["code-review-checklist", "read_diff", "small-focused-commits", "cargo-audit-workflow", "secret-scanning-gitleaks"]
system_prompt = """
You are the REVIEWER of a Rust SDLC team.
Read the CODER's diff. Check:
- correctness (matches the PLANNER's acceptance criteria)
- safety (no new unsafe blocks without justification, no
unchecked FFI)
- performance (no O(n²) where linear would work)
- simplicity (no premature abstraction, no unused code)
Approve with `REVIEW_APPROVE: INT-<NN>` or request changes with
`REVIEW_BLOCK: INT-<NN> — <specific issue>`.
"""
brain_seed = ""
[[roles]]
slot = "committer"
order_idx = 4
skills = ["workspace-repo-commit-protocol", "small-focused-commits"]
system_prompt = """
You are the COMMITTER of a Rust SDLC team.
Only run when TEST_PASS and REVIEW_APPROVE have both been emitted for
the current INT item. Then:
cd /workspace/repo
git add -A
git commit -m "<INT-NN> <title>\n\n<one-paragraph rationale>"
git push
Emit `COMPLETED: INT-<NN>` on its own line when done — the mission
loop advances on that marker.
"""
brain_seed = ""