cpliakas/claude-code-engineering-leaders

refine-story

Score a story draft against INVEST criteria and eight agile coaching principles. Returns a structured report with pass/fail per dimension and specific rewrites or corrective actions for failures.

原文の言語: 英語

write-convention

Route convention authorship to the declared domain owner. Accepts an optional --domain=<value> flag or positional domain token. Valid domains: tactical-implementation, infrastructure, quality, ux, architecture. Defaults to tactical-implementation when…

原文の言語: 英語

add-specialist

Register a specialist agent in the Tech Lead's routing model. Use when adding a new agent to the project that the Tech Lead should consult during implementation planning, incident analysis, or retrospectives.

原文の言語: 英語

audit-routing-quality

Audit the Tech Lead's specialist routing quality by reading the ## Routing Outcomes history and recommending narrowing actions for over-routed specialists. Complements /audit-routing-table (structural hygiene) with outcome-based data. Advisory only: never…

原文の言語: 英語

plan-implementation

Drive the Tech Lead's two-phase implementation planning protocol end-to-end. Accepts a story or issue reference, invokes the Tech Lead for Phase 1 routing, spawns each matched specialist as a sub-agent in parallel, then re-invokes the Tech Lead for Phase 2…

原文の言語: 英語

onboard

Use when setting up the engineering-leaders plugin for the first time on a project, or when re-running onboarding to update shared project context. Gathers shared project context for all agents (one question at a time) and discovers specialist plugins for the…

原文の言語: 英語

re-onboard

Audit onboarded agent memory for drift against live project signals. Use when you want to re-onboard, detect onboarding drift, refresh project context, check for stale memory, or run an onboarding drift check. Compares each agent's project memory against…

原文の言語: 英語

audit-agent-memory

Audit a single agent's project memory directory for hygiene issues. Use when you want to run agent memory hygiene checks, audit memory, inspect bloated memory, or detect state-like content, dead links, or oversized memory files. Complements…

原文の言語: 英語

audit-routing-table

Audit the Tech Lead's specialist routing model for orphan overrides, broken file pointers, redundant overrides, and thin agent descriptions. Reports findings for human review — does not auto-correct. Use after onboarding, after adding specialists, or when the…

原文の言語: 英語

conduct-postmortem

Conduct a blameless postmortem for an incident or failed/aborted release. Collects evidence and produces a structured postmortem document. Use when the user invokes /conduct-postmortem, says "postmortem", "incident retrospective", "release blocked", or…

原文の言語: 英語

facilitate-retrospective

Facilitate a structured retrospective from a sprint or body-of-work description. Follows the Derby-Larsen five-phase framework with blameless framing and SMART action items.

原文の言語: 英語

refinement-review

Convene the Product Owner, Chief Architect, and UX Strategist in parallel on a story draft and produce a consolidated readiness verdict. Use before /plan-implementation to surface scope, architectural, and persona-fit concerns while the story is still cheap…

原文の言語: 英語

onboard-product-owner

Use when configuring the Product Owner agent for a specific project. Gathers issue tracker details, backlog norms, and current roadmap state, then writes them to the Product Owner's project memory. Run /onboard first to establish shared project context. This…

原文の言語: 英語

analyze-code-churn

Analyze code churn and thrash patterns in a git repository. Produces a structured report with hotspot detection, rework classification, temporal coupling, and severity-rated findings. Use for SDLC health checks, sprint retrospectives, or when recurring…

原文の言語: 英語

decompose-requirement

Decompose a requirement into well-sequenced child items. Takes an epic and produces stories, or takes a story and produces subtasks.

原文の言語: 英語

plan-test-strategy

Produce a test strategy for a feature, component, or story. Identifies the highest-impact tests by type and layer, flags brittleness risks, and recommends what NOT to test. Use for test planning, coverage gap analysis, or when deciding how to test a new…

原文の言語: 英語

write-adr

Produce a complete ADR (Architecture Decision Record) document in MADR format. Use when the user invokes /write-adr, the Chief Architect recommends recording a decision, or an architectural review surfaces decisions to document.

原文の言語: 英語

write-bug

Scaffold a RIMGEN-validated bug report with reproduction steps, environment context, severity, and priority. Outputs named warnings for any missing or incomplete RIMGEN sections.

原文の言語: 英語

write-epic

Write an epic specification with a problem statement, success criteria, and scope boundaries.

原文の言語: 英語

write-runbook

Generate a structured operational runbook for incident response, diagnostics, or maintenance procedures. Use when defining a runbook for a new alert, documenting a post-incident gap, establishing an operational procedure, or preparing a maintenance checklist.

原文の言語: 英語

write-spike

Produce a structured findings document for a topic too uncertain to story-write directly. Covers problem restatement, key questions, options considered, findings, remaining unknowns, and a story seed.

原文の言語: 英語

write-story

Write a well-structured user story with acceptance criteria and INVEST validation.

原文の言語: 英語