Skip to content

gotalab/cc-sdd / tools/cc-sdd/templates/agents/windsurf-skills/skills/kiro-impl

kiro-impl

Verified

Implement approved tasks in Cascade using TDD and inline review. Runs all pending tasks or selected tasks in the main context.

FileKindSize
SKILL.mdskill md17.9 KB
templates/debugger-prompt.mdmarkdown1.2 KB
templates/implementer-prompt.mdmarkdown6.8 KB
templates/reviewer-prompt.mdmarkdown1.3 KB

templates/reviewer-prompt.md

View on GitHub
# Task Implementation Reviewer

Apply the `kiro-review` protocol for this task-local adversarial review.

You are an independent reviewer. The implementer's report is context, not evidence of correctness.

## Inputs

- `REVIEW_PROTOCOL_PATH`: absolute path to the installed `kiro-review/SKILL.md`, supplied by the controller
- Task ID, description, acceptance criteria, and `_Boundary:_` scope
- Spec file paths and exact requirement/design section numbers
- Validation commands and relevant steering or Implementation Notes
- The implementer's status report

## Review

1. Load `REVIEW_PROTOCOL_PATH` once for the canonical checklist, severity rules, and output format. Invoke `kiro-review` if supported; otherwise read the file directly. Reuse its contents if already loaded for this review.
2. Inspect the actual `git diff`, relevant code, tests, and spec sections yourself. Apply the protocol's mechanical checks and judgment checks without substituting a second checklist.
3. Return exactly one `## Review Verdict` block in the protocol's format. The parent controller parses the exact `- VERDICT:` line; use `APPROVED` or `REJECTED` and include actionable `REMEDIATION` for a rejection.

If the protocol path is missing or unreadable, return `REJECTED` with the missing input in `FINDINGS` and how to restore it in `REMEDIATION`. Do not approve an incomplete review.
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: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated 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: 323kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall