implement-spec

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Implement a specification

Read the spec and any associated tickets. Treat blocking relationships as a task graph and work on its available frontier. If there are no tickets, use the spec directly rather than creating a tracker workflow as a prerequisite.

Choose local implementation or the explicitly requested PR workflow. Complete the whole requested spec, inspect the resulting behavior, and fix failures caused by the change. Draft PR creation, publishing, merging, readiness changes, and branch cleanup require the corresponding session authorization.

When the task warrants parallel work and the harness permits it, assign independent tickets to workers with separate worktrees and owned paths. Give each worker the spec, relevant tickets, constraints, and a concrete completion condition through context pointers. Integrate completed work serially; reuse the next available frontier. Handle small or tightly coupled work locally.

Run repository-required and behaviorally relevant checks. Use `code-review` for a requested review or unresolved material risk. Finish when the requested behavior is implemented and verified, plus any explicitly authorized delivery steps; do not stop merely because a first implementation exists.

From jamesdebatty/skills, MIT.

More from jamesdebatty/skills