@bonesofspring/ai-rules 0.2.14 → 0.2.16

package/presets/claude/android-kotlin/commands/technical-retro.md

@@ -0,0 +1,85 @@
+---
+name: technical-retro
+description: Facilitate a technical retrospective for a period, incident, release, or completed agent-team task slug.
+---
+
+# Technical retro
+
+Act as a **neutral technical retrospective facilitator**, not a code reviewer or people evaluator. Use skill **`technical-retro`** as the primary playbook.
+
+## When to run
+
+- User asks for: “retro”, “technical retro”, “sprint/iteration review”, “action items after release”.
+- After an agent-team pipeline completes (`/feature-start` → `/feature-continue`).
+- Context exists: period, topic (release, incident), task slug, notes.
+
+## Inputs (collect, do not invent)
+
+Ask when missing:
+
+- **Period and focus**.
+- **Task slug** (if the retro covers agent-team work).
+- **Participants/roles** (when relevant).
+- **Constraints**: time, format (async vs sync).
+
+### Agent-team artifacts (when there is a slug)
+
+Read from the repository:
+
+- `.claude/team/tasks/<slug>/pipeline.json`
+- `.claude/team/tasks/<slug>/brief.md`
+- `.claude/team/tasks/<slug>/decomposition.md`
+- `.claude/team/tasks/<slug>/status.json`
+- Git diff / `git status` for changed files
+
+Do not attribute facts that are not in artifacts, the diff, or the user message.
+
+## Facilitation principles
+
+- **Safety**: process and system, not “blame”.
+- **Specifics**: from abstractions to observable events.
+- **Balance**: positives and growth areas.
+- **Action items**: owner and due date for each.
+- **Do not mix with code review** — keep blocks separate if both are requested.
+
+## Default session structure
+
+1. **Goal and frame**.
+2. **Gather facts**: went well / got in the way / surprises.
+3. **Theme clustering** (3–7).
+4. **Root causes** for 1–2 painful themes.
+5. **Experiments** (1–3 process changes).
+6. **Action items**: what / owner / by when / success criterion.
+
+## “Agent work” block (required when there is a slug)
+
+If the retro relates to a `/feature-start` pipeline:
+
+| Question | What to capture |
+|----------|-----------------|
+| Router | Wrong intent, extra/missing steps in pipeline |
+| Analyst | Bad assumptions, missed AC, extra/missing tasks |
+| Decomposition | Incomplete layer coverage, wrong order, blocked dependencies |
+| Developer | Scope creep, missed rules, lint/type gaps |
+| Reviewer | Missed defects, false positives, checklist quality |
+| QA | AC coverage by tests, flakiness, gaps in e2e plans |
+
+**Action items** in this block — improve **prompts, subagents, and rules** (not only code).
+
+## Response format
+
+- Header: period, focus, slug (if any), assumptions.
+- Agenda by stages.
+- **“Agent work”** block (when applicable).
+- Themes — bullets; disputed items — **questions for the team**.
+- **Action items** at the end.
+
+## Constraints
+
+- Do not invent quotes and facts without input.
+- Do not give HR recommendations.
+- If only a template is requested — **agenda template** without invented content.
+
+### Metrics evidence
+
+When `metrics.json` exists, run the local aggregation script and report the cohort, sample size, incomplete artifacts, attribution confidence, active attempt duration, and human-gate wait separately. Do not treat gate wait or malformed ledgers as agent duration.

package/presets/claude/android-kotlin/hooks/README.md

@@ -0,0 +1,16 @@
+# `.claude/hooks` (preset android-kotlin)
+
+| File | Purpose |
+|------|---------|
+| `chain-team-phases.sh` | Pipeline chaining after subagent stop (`TEAM_ROOT=.claude/team`) |
+| `guard-shell-command.sh` | Destructive git / package-manager guard; **allows** `./gradlew` / `simctl` / `xcrun` |
+
+Claude Code may not use Cursor `hooks.json`. Wire scripts per project docs when enabling agent-team auto-chain.
+
+**No `hooks.json` in Claude preset** (platform limit — same as next Claude).
+
+## Optional cookbook
+
+Example scripts live in `hooks/examples/` (secret-guard, format-edited, test-on-save). They are **not** auto-enabled.
+
+To wire in Claude Code: copy an `.example.sh` into `hooks/`, make executable, and register per [Claude Code hooks](https://code.claude.com/docs/en/hooks) for your project. Keep stack-safe recipes (this preset: **android-kotlin**). Cursor twin examples under `presets/cursor/android-kotlin/hooks/examples/` are the same allowlist forks.