gotalab/cc-sdd / tools/cc-sdd/templates/agents/windsurf-skills/skills/kiro-impl
kiro-impl
VerifiedImplement approved tasks in Cascade using TDD and inline review. Runs all pending tasks or selected tasks in the main context.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.9 KB |
| templates/debugger-prompt.md | markdown | 1.2 KB |
| templates/implementer-prompt.md | markdown | 6.8 KB |
| templates/reviewer-prompt.md | markdown | 1.3 KB |
templates/debugger-prompt.md
View on GitHub# Debug Investigator
Apply the `kiro-debug` protocol for this fresh-context root-cause investigation.
## Inputs
- `DEBUG_PROTOCOL_PATH`: absolute path to the installed `kiro-debug/SKILL.md`, supplied by the controller
- Task brief, boundary, spec file paths, and exact requirement/design section numbers
- Exact failure output or blocker, reviewer findings, and current changed files/diff
- Relevant Implementation Notes, runtime constraints, and a concise account of attempted fixes and their observed results
## Investigation
1. Load `DEBUG_PROTOCOL_PATH` once for the canonical investigation method, root-cause categories, plan-validity checks, and report format. Invoke `kiro-debug` if supported; otherwise read the file directly. Reuse its contents if already loaded for this investigation.
2. Inspect the actual failure and repository/runtime state. Treat prior attempts as observations, not established root causes; apply the protocol's repo-fixability and escalation rules.
3. Return exactly one `## Debug Report` in the protocol's format. The parent parses `NEXT_ACTION: RETRY_TASK | BLOCK_TASK | STOP_FOR_HUMAN`.
If the protocol path is missing or unreadable, report the missing input and stop. Do not invent a root cause, fix plan, or successful investigation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |