SebastienDegodez/skraft-plugin
Agent
The discoverer applies explicit review criteria for every triage decision. No subjective classification: every label, every priority level is defended by evidence from the issue and project context.
SebastienDegodez/skraft-plugin
Agent
The reviewer is strictly read-only. It applies CQS to ensure that evaluating an artifact does not transform it.
SebastienDegodez/skraft-plugin
Agent
The planner treats scope, time, and quality as conscious variables. Each story is sized to be deliverable in one complete pipeline cycle — no more, no less.
SebastienDegodez/skraft-plugin
Agent
Reverse-engineers an existing codebase into an HVE-format PRD. Standalone workflow the human invokes directly, decoupled from the orchestrator.
SebastienDegodez/skraft-plugin
Agent
Makes a brownfield service SAFE TO CHANGE before refactoring: API contracts, Microcks mocks, golden-master characterization tests. Standalone workflow.
SebastienDegodez/skraft-plugin
Agent
Drives a disciplined refactor (Mikado or Strangler Fig) of a brownfield component that already has a safety net, keeping it green at every commit. Standalone workflow.
SebastienDegodez/skraft-plugin
Agent
All SKRAFT pipeline agents: role, phase, reviewer.
SebastienDegodez/skraft-plugin
Agent
The orchestrator is a pure coordinator. It owns no business logic, no artifact-writing capability. This separation applies CQS at the system level: commands go to executors, queries come back from reviewers.
SebastienDegodez/skraft-plugin
Agent
This page is not an agent to invoke — it documents the DELIVER loop combining the software-engineer and the software-engineer-reviewer.
SebastienDegodez/skraft-plugin
Agent
The DELIVER reviewer is adversarial by design. Four independent lenses (architecture, tests, code, business) evaluate the deliverable without coordinating — the verdict is a weighted synthesis, not a consensus.
SebastienDegodez/skraft-plugin
Agent
Implementation starts with acceptance tests, not with code. The Walking Skeleton ensures a complete functional slice exists before enriching details.
SebastienDegodez/skraft-plugin
Agent
The architectural reviewer applies CQS: it queries artifacts without modifying them. This constraint prevents the reviewer from silently "patching" a flawed architecture — it must explicitly reject it.
SebastienDegodez/skraft-plugin
Agent
The architectural model is not a decorative diagram — it is a communication tool between developers and domain experts. The Event Model captures system behaviour in a shared language.
SebastienDegodez/skraft-plugin
Agent
The researcher produces truth, not plausible code. Its constraint — never implement — is what makes its findings trustworthy. A team that skips the investigation phase pays for it during DESIGN: the architect decides under uncertainty, the software engineer discovers the surprise mid-sprint.
SebastienDegodez/skraft-plugin
Plugin Claude Code
skraft SDLC pipeline — agents, skills and instructions for outside-in TDD, Clean Architecture and the DISCOVER→DELIVER workflow.
SebastienDegodez/skraft-plugin
Hook Claude Code
Runs when a session starts, executing housekeeping.mjs via node. From SebastienDegodez/skraft-plugin.
SebastienDegodez/skraft-plugin
Hook Claude Code
Runs before the agent uses a tool for Agent and Bash tool calls, executing hook.mjs via node (2 commands). From SebastienDegodez/skraft-plugin.
SebastienDegodez/skraft-plugin
Hook Claude Code
Runs when a subagent starts, executing hook.mjs via node. From SebastienDegodez/skraft-plugin.
SebastienDegodez/skraft-plugin
Hook Claude Code
Runs when a subagent finishes, executing hook.mjs via node. From SebastienDegodez/skraft-plugin.
SebastienDegodez/skraft-plugin
Hook Claude Code
Runs after a tool call finishes for Agent and Read tool calls, executing hook.mjs via node (2 commands). From SebastienDegodez/skraft-plugin.
SebastienDegodez/skraft-plugin
Skill Claude CodeCodex
Use when reviewing DISTILL artefacts (Gherkin scenarios, test plans, implementation plans) for quality, completeness, and alignment. Contains the gate definitions and scoring rubric for the acceptance-designer-reviewer lenses.
SebastienDegodez/skraft-plugin
Skill Claude CodeCodex
Use when deciding WHETHER a candidate architectural choice deserves an architecture decision record, before any record is drafted: a story enters DESIGN with a list of candidate choices, a reviewer flags ADR inflation, or someone asks "should I write an ADR for X?", "how many ADRs does this story need?", "is this…
SebastienDegodez/skraft-plugin
Skill Claude CodeCodex
Use when reviewing a phase artifact — a discovery brief, a plan, a design, an acceptance specification, or a slice reported as delivered — and the review has to end in a defensible pass-or-block verdict rather than a list of remarks. Covers judging whether the artifact covers everything that fed into it, whether it…
SebastienDegodez/skraft-plugin
Skill Claude CodeCodex
Use when documenting architecture decisions as ADRs, evaluating trade-offs between alternatives, or managing the lifecycle of existing decisions. Covers ADR template, status transitions, consequence analysis, and quality criteria.