Os Small
Quick autonomous implementation of a small GitHub issue
Claude CodeGeneric
---
description: Quick autonomous implementation of a small GitHub issue
argument-hint: <issue-number>
allowed-tools:
- Task
- TodoWrite
- Bash
- Read
- Write
- Edit
- Glob
- Grep
---
# One Shot Small: $ARGUMENT
## Initialize TodoWrite Progress Tracking
Use TodoWrite to create this checklist:
- Retrieve GitHub issue and setup branch
- Implement feature with tests
- Run quality checks
## PHASE 1: Setup
*Mark "Retrieve GitHub issue and setup branch" as in_progress*
### Step 1.1: GitHub Issue and Git Setup
EXECUTE:
- Fetch issue: gh issue view $ARGUMENT --json number,title,body,labels
- git stash
- git checkout master
- git pull
- Derive branch name: TITLE=$(gh issue view $ARGUMENT --json title -q .title) CLEAN=$(echo "$TITLE" | tr '[:upper:]' '[:lower:]' | tr -cs '[:alnum:]' '-' | cut -c1-50) BRANCH="feature/$ARGUMENT-${CLEAN}"
- git checkout -b $BRANCH
- mkdir -p docs/tickets/$ARGUMENT
ACTIONS:
- Write GitHub issue content to docs/tickets/$ARGUMENT/ticket.md (including title, state, body)
- Create docs/tickets/$ARGUMENT/tasks.md with simple structure:
Implementation Tasks
- Implement feature
- Write unit tests
- Create E2E tests (if applicable)
VERIFY: Branch created, documentation present
*Mark "Retrieve GitHub issue and setup branch" as completed*
## PHASE 2: Implementation
*Mark "Implement feature with tests" as in_progress*
### Step 2.1: Parallel Implementation [EXECUTE IN PARALLEL]
LAUNCH 2 AGENTS IN PARALLEL:
AGENT 1: full-stack-engineer PROMPT FOR AGENT: "Quick implementation of issue #$ARGUMENT:
- Read docs/tickets/$ARGUMENT/ticket.md
- Implement the feature following CLAUDE.md guidelines
- Write unit tests (co-located .test.ts files)
- Ensure >80% test coverage on new code
- Update docs/tickets/$ARGUMENT/tasks.md marking implementation tasks as [x] Keep it simple and focused."
AGENT 2: test-engineer PROMPT FOR AGENT: "Create E2E tests for issue #$ARGUMENT if applicable:
- Read docs/tickets/$ARGUMENT/ticket.md
- If user journey involved, create E2E test in e2e-tests/
- Include accessibility checks with axe-core
- If no E2E test needed, mark task as N/A
- Update docs/tickets/$ARGUMENT/tasks.md DO NOT run tests yet."
WAIT FOR BOTH AGENTS TO COMPLETE
*Mark "Implement feature with tests" as completed*
## PHASE 3: Quality Checks
*Mark "Run quality checks" as in_progress*
### Step 3.1: Run Tests
EXECUTE IN SEQUENCE:
- yarn lint
- yarn dev (verify boots - kill after 10 seconds)
- yarn test
- yarn test:e2e
IF FAILURES:
- Fix e2e tests with test-engineer, everything else with full-stack-engineer agent
- Re-run failed tests
- Repeat until passing
VERIFY: All checks pass
*Mark "Run quality checks" as completed*
## COMPLETION CHECK
FINAL VALIDATION:
- Feature implemented
- Tests passing (lint, unit, e2e)
- Tasks.md reflects completion
- No obvious quality issues
## Success Output
"Quick implementation of issue #$ARGUMENT complete:
- ✅ Feature implemented
- ✅ Tests written and passing
- ✅ Quality checks passed
Documentation: docs/tickets/$ARGUMENT/
Branch: feature/$ARGUMENT-[name]
Ready for PR creation or manual review."
Maintain Os Small?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[Os Small on getagentictools](https://getagentictools.com/loops/hmcts-one-shot-small-argument?ref=badge) npx agentictools info loops/hmcts-one-shot-small-argument The second line is the CLI lookup for this page — handy in READMEs and docs.