Implement an approved feature specification. Triggered by a routine when a spec PR is merged with the `ai:implement` label (per ADR 057), or by a human asking "implement SPEC-NNN" interactively. Follows the spec's implementation order using TDD, logs deviations, runs the full verification suite, opens an implementation PR with label `ai:done`, and closes out the spec with post-implementation notes and tech debt capture.
78
90%
Does it follow best practices?
Impact
100%
2.56xAverage score across 1 eval scenario
Advisory
Suggest reviewing before use
{
"context": "Tests whether the agent correctly documents the pre-flight procedure, branch naming convention, tool conventions (git+pnpm locally, mcp__github__* remotely, no gh CLI), spec review gate verdicts, and the complete blocked escalation protocol.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Branch naming pattern",
"description": "pre-flight-checklist.md specifies the branch name format as 'claude/impl-NNN-<slug>' (matching this exact pattern, not a variant like 'feature/', 'impl/', or without the 'claude/' prefix)",
"max_score": 8
},
{
"name": "Spec status set In Progress",
"description": "pre-flight-checklist.md includes the step of setting the spec status to 'In Progress' as the first commit on the implementation branch",
"max_score": 8
},
{
"name": "Blocked verdict stops work",
"description": "pre-flight-checklist.md specifies that a 'Needs revision' or 'Blocked' verdict from the spec review causes implementation to STOP (not proceed with warnings)",
"max_score": 10
},
{
"name": "Warnings proceed with notes",
"description": "pre-flight-checklist.md specifies that Warnings from the spec review allow implementation to continue, with warnings acknowledged in the implementation notes file",
"max_score": 8
},
{
"name": "principles plugin best-effort",
"description": "pre-flight-checklist.md describes the engineering-principles plugin as best-effort: if unavailable, note it (as principles_unavailable=true or equivalent) and continue rather than blocking",
"max_score": 8
},
{
"name": "No gh CLI",
"description": "tool-conventions.md explicitly states that the 'gh' CLI is NOT used for remote GitHub operations",
"max_score": 10
},
{
"name": "mcp__github__* for remote ops",
"description": "tool-conventions.md specifies mcp__github__* tools for remote GitHub operations",
"max_score": 10
},
{
"name": "Slack DM tool and channel",
"description": "tool-conventions.md or escalation-protocol.md specifies mcp__claude_ai_Slack__slack_send_message with channel $SLACK_NOTIFY_USER for blocker DMs",
"max_score": 10
},
{
"name": "ai:blocked label target",
"description": "escalation-protocol.md specifies applying 'ai:blocked' to the open impl PR, OR to the source SPEC PR if no impl PR exists yet",
"max_score": 10
},
{
"name": "PR comment content",
"description": "escalation-protocol.md specifies the PR comment must contain: one-line problem statement, one-line proposed resolution, and a link to verification output or offending diff",
"max_score": 10
},
{
"name": "No silent partial branches",
"description": "escalation-protocol.md states that partial-state branches must NOT be pushed without a draft PR plus a blocker comment",
"max_score": 8
}
]
}