Implement work described in a specification or task tickets, using test-driven development where possible. Check types and individual tests during development, run the full test suite at the end, review the changes, and commit to the current branch.
Implement a piece of work based on a spec or set of tickets.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Implement the work described by the user in the spec or tickets.
Use /tdd where possible, at pre-agreed seams.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Once done, use /code-review to review the work.
Commit your work to the current branch.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Turn an initial idea into an agreed design before coding. The skill clarifies goals and constraints through focused questions, compares possible approaches, and produces a reviewed specification ready for implementation planning.
Review code changes from a chosen Git reference against both project coding standards and the original requirements. Separate agents examine each perspective in parallel, and the results stay separate so specification gaps and coding issues are visible.
Start or resume a development workflow by checking the request and current change state. Routes work through proposal, design, implementation, verification, and archiving, with separate paths for bug fixes and smaller changes and pauses for required user decisions.
Guide a development change through requirements, design, implementation, verification, and archiving. Comet combines OpenSpec for specifications with Superpowers for technical work, detects the current phase, and routes the agent to the appropriate next step.
Routes a Comet request to the Native or Classic workflow based on project settings. When project settings are missing, it saves the global defaults locally so later changes to those defaults do not alter the project's choice.
Start a Comet task without choosing Native or Classic yourself. This entry skill reads the project’s workflow configuration, activates the configured option, and forwards the original request unchanged to the matching skill so work follows the project’s saved settings.