Skip to content

Huruikagi/pc-build-planner / .agents/skills/sb-implement

sb-implement

Verified

Implement or resume one roadmap item — executing a Spec's approved task plan through returned review or diagnosis with dispatched implementers and reviewers, or performing and completing a Direct change. Do not use for a diagnosis-only request asking why work failed or cannot be implemented.

FileKindSize
SKILL.mdskill md5.7 KB
agents/openai.yamlconfig204 B
references/direct.mdmarkdown4.4 KB
references/spec-backed.mdmarkdown11.0 KB

references/direct.md

View on GitHub
# Implement a Direct item

Read `specbind milestone scope --include-body` and the current
`specbind milestone review status` before implementation. If shared changes are
planned, require a fresh review. If their review is missing/stale/invalid, route to
`sb-plan --shared` and stop before changing implementation. A fresh review is
required for shared-agreement changes even in a Direct-only milestone.
Read `specbind contract shared read` when the item uses shared resources and
verify their applicable invariants with the actual project checks. A normal
content change within the agreement does not rewrite the shared Contract.
Never author shared agreements during Direct implementation.

There is no approved task plan to dispatch. Implement the Roadmap item's summary
in this context, against the repository's existing conventions. Before writing,
state the observable done condition and the applicable project checks. If the
summary leaves a product or architecture decision you cannot make narrowly,
stop and route it through discovery; Direct is not permission to invent the
missing canonical artifacts.

Review the resulting diff under the run's selected mode. Direct work defaults to
`inline` when the invocation supplied no explicit `--review` value; there is no
separate project setting to discover. `inline` applies the correctness and
weakened-verification standard from `task-review` here, using the Roadmap summary
as the obligation. `required` dispatches a fresh reviewer with that summary, the
actual diff, the checks, and the protocol; `off` skips only this run-scoped
review. A rejection may return to implementation at most twice. `CANNOT_REVIEW`
and an unresolved rejection enter the same bounded diagnosis route as
Spec-backed work.

When `required`, use the registered `specbind-reviewer` role when available,
with an ordinary fresh subagent as the fallback.

```sh
specbind protocol read task-review
```

## Checkpoint the Direct item

This step is only for a Direct item. Spec-backed Task checkpoints run inside the
other procedure. A Direct item must establish the clean committed revision
before the completion handshake. Do not skip ahead and return here afterwards.

```sh
specbind adapter read git --for consume
```

`NO_CHANGE ADAPTER_ABSENT` or `NO_CHANGE ADAPTER_SCAFFOLD` means there is no
adapter-directed commit. Stop there — that is an answer, not a missing file to
work around.

When the adapter has guidance, follow it. The request to perform this mutating
phase authorizes the adapter's narrow local checkpoint as its ordinary final
step. It does not authorize anything broader:

- An explicit user or root instruction that forbids commits wins, and tool
  permissions still apply.
- Commit guidance is not push guidance. Push only where the adapter says to, and
  never force-push, rewrite history, or bypass a protected branch.
- Stage only the paths this run produced. Unrelated work already in the worktree
  is left exactly as it is.
- Stop before the Git operation if the guidance is ambiguous, unsafe, or
  conflicts with something else you were told.

## Complete after the checkpoint

There is no later Spec-level validation for Direct work, so this run finishes
the item. Preflight needs the reviewed implementation at a **clean committed
`HEAD`**. Do not manufacture one. If the checkpoint produced no commit because
the adapter gave no usable guidance or you lacked authority, say completion
needs a commit and stop; the Roadmap item remains pending.

Otherwise obtain the committed revision and run, in this order:

```sh
specbind milestone direct preflight <direct>
specbind milestone direct complete <direct> --implementation-revision <revision>
```

Do not stop merely because the implementation commit succeeded. The successful
handshake is what records the Direct item complete. If project policy also asks
for completion metadata or checkpoints after every eligible workflow unit,
re-read the Git adapter and apply it once more to the CLI-owned Roadmap change
after completion. This is a separate metadata checkpoint; never amend it into
the clean implementation revision used by preflight.

Adapter guidance is closed-world authority. An absent or scaffolded adapter, or
active guidance limited to implementation paths, does not authorize the
Roadmap checkpoint. In that case the Direct item is still completed, but report
the modified Roadmap path, that `Revision` is unavailable until it is
reconciled, and the exact adapter reason for leaving it uncommitted.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall