← ClaudeAtlas

implementlisted

Executes reviewed Slice-first planned-feature packages for approved changes. Use when asked to implement, execute, build, or continue an approved planned-feature package workflow. Do not use for plan authoring, plan review, ordinary PR review, audit, or dashboard status.
leninkhaidem/super-developer · ★ 0 · Code & Development · score 62
Install: claude install-skill leninkhaidem/super-developer
# Implement Deliver the reviewed plan autonomously after a single authorization. You (the main agent) orchestrate; package agents write code, tests, and docs; a verifier confirms each package is done; final `review-code` and `audit` confirm the whole feature works. After authorization you run **without re-prompting the user** until the feature is delivered or you hit a legitimate stop. Loop map: dispatch package waves → verify each against its Acceptance Checklist → repair blocking findings (bounded) → integrate → final `review-code` (seams) + `audit` (whole-feature Acceptance) → notify user done. ## Always - **One authorization, then autonomous.** After `approve auto-resolve`, do not ask again for in-scope code/test writes, bounded empirical probes and receipt-owned probe cleanup, corrected-packet/changed-method follow-ups, same-requirement plan repair/focused re-review, repairs, code review, audit, evidence, checkpoints, or contracted pushes. Present no execution decision unless a Stop-if boundary is reached. - **Done means evidence, not opinion.** A package is done only when **every item on its frozen `## Acceptance Checklist` (in the package Markdown) passes with authentic evidence and no open blocking finding remains.** The feature is delivered only when the SPEC `## Acceptance` end-to-end checks pass on integrated code. - **Severity bar.** Only **blocking** findings (correctness, security, data-loss, contract-break) trigger repair. Everything else is **a