All authors

Claude Skills by MageByte-Zero
github.com/MageByte-Zero9 skills0 installs12 views
- Bug InvestigatorUse when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.Votes: 0GitHub stars: 819
- Build ExecutorExecute an active direct request or approved planned change. Native continuous implementation is the default; existing legacy changes retain their recorded contract obligations.Votes: 0GitHub stars: 819
- Code ReviewerReview completed implementation batches for spec compliance and code quality. Invoke after execution batches complete, before merging, or when a review gate is reached in the workflow.Votes: 0GitHub stars: 819
- Contract BuilderMaintain an execution contract only for an existing legacy change that requires one. New direct/planned changes do not invoke this skill when a contract is absent.Votes: 0GitHub stars: 819
- Need ExplorerClarify intent, scope, constraints, and success criteria before artifact creation. Invoke when the request is fuzzy, the user is comparing options, or the workflow needs a stable change definition before writing artifacts.Votes: 0GitHub stars: 819
- Release ArchivistClose out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.Votes: 0GitHub stars: 819
- Spec MergerSync delta specs to main specs before closure. Invoke while an executing change has delta specs to merge into the main spec base, or when detecting spec drift across multiple changes.Votes: 0GitHub stars: 819
- Spec WriterCreate or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.Votes: 0GitHub stars: 819
- Workflow StartPrimary entry point for the spec-superflow state-machine workflow. Invoke only when the user explicitly requests spec-superflow or an active change contains .spec-superflow.yaml and the user asks to continue that change. Generic proposal, specs, design, task, or contract files are not activation signals.Votes: 0GitHub stars: 819