Agent skill

implement-spec-subagent

Implements a single ticket from a spec. Always invoke with ticket, spec file, progress file. For use by subagents only.

Stars 8
Forks 1

Install this agent skill to your Project

npx add-skill https://github.com/rstacruz/agentic-toolkit/tree/main/skill/atk/implement-spec-subagent

SKILL.md

Input Validation

CRITICAL: This skill requires three inputs to be passed from the parent agent:

  1. {{TICKET}} - The ticket ID and title (e.g., "T-01: Implement user authentication")
  2. {{SPEC_FILE}} - Path to the spec file (e.g., artefacts/spec.md)
  3. {{PROGRESS_FILE}} - Path to the progress file (e.g., artefacts/progress.md)

If any of these inputs are missing or not provided, exit immediately with this message:

Error: Missing required input. Please provide: ticket ID, spec file path, and progress file path.

Do not proceed further. Do not attempt to infer or guess missing values.

Workflow

  1. Gather context

    • Read progress file ({{PROGRESS_FILE}})
    • Read spec file(s) ({{SPEC_FILE}})
  2. Do ticket

    • Ticket: {{TICKET}}
    • See guidelines below
    • Proceed to step 3 as soon as the ticket is done, don't proceed to other tickets
  3. Verify work

    • Stage updates in Git (git add)
    • Load $review-changes skill. Ask it to review staged changes (git diff --cached).
    • Assess feedback. Address any P1 issues that makes sense to do.
    • If there was feedback, ask reviews again, then address again. Keep looping until there are no more changes to do.
  4. Verify single ticket scope

    • Confirm you only modified files related to ONE ticket
    • If you touched multiple tickets, undo changes and redo with single ticket focus
  5. Document learnings

    • Assess the conversation, summarise work done, include assumptions flagged
    • Identify potential roadblocks that future dev work might encounter (eg, errors, wrong decisions)
    • Append them to progress file - this is to assist future work
  6. Commit changes

    • Include ticket ID in commit title

Code writing guidelines

  • State assumptions before writing code.
  • Verify before claiming correctness.
  • Handle non-happy paths as well. Do not handle only the happy path.
  • Answer: under what conditions does this work?

Other guidelines

  • Do not make a pull request
  • IMPORTANT: Only do ONE ticket. Stop after finishing one ticket. Do not proceed to others.
  • IMPORTANT: Never commit artefacts/ files.

Expand your agent's capabilities with these related and highly-rated skills.

rstacruz/agentic-toolkit

refine-implementation

Use after implementation to simplify and review code. Provide: git range (eg, main...HEAD). Runs simplify + peer review loop until change set is clean.

8 1
Explore
rstacruz/agentic-toolkit

implement-spec

Implements a spec on a ticket-by-ticket basis.

8 1
Explore
rstacruz/agentic-toolkit

spec-product-requirements

Gives important guidelines to define product requirements sections (functional requirements, technical requirements, constraints, design considerations, diagrams). Companion to $spec-mode.

8 1
Explore
rstacruz/agentic-toolkit

coding-practices

Contains important guidelines for software engineering, coding, programming. Includes (but not limited to): - CP1: Functional core, imperative shell - CP2: Operational vs unexpected errors - CP3: Result-oriented interface pattern - CP4: Presentational vs container components - CP5: Log context builder pattern Use this when writing, editing, debugging, planning, or otherwise working with: - Any programming work - UI components in React, Vue, or similar - JavaScript, TypeScript, Rust, or any programming language

8 1
Explore
rstacruz/agentic-toolkit

spec-tech-design

Gives important guidelines to define technical design sections (call graphs, data models, pseudocode, files, CSS classes, testing strategy). Companion to $spec-mode skill.

8 1
Explore
rstacruz/agentic-toolkit

review-changes

Use when reviewing code changes against a plan. Provide: plan/spec doc; git range or changed files (eg, branch...HEAD). Returns P1/P2/P3 on alignment, quality, bugs, security.

8 1
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results