spec-implementlisted

Use when the tasks exist and it is time to build - "go ahead", "start on it", "implement this". Executes them in order, tests before the code they cover, one phase at a time.
repository-standards/core · ★ 3 · Testing & QA · score 76

Install: claude install-skill repository-standards/core

## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). ## Outline 1. Run `scripts/spec/check-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").  The resolved `FEATURE_DIR` comes from a persisted pointer (`specs/feature.json`), not from `$ARGUMENTS`. If `$ARGUMENTS` names a capability, or a prior message in this conversation did, confirm the resolved directory actually matches before writing any code - especially at the start of a fresh session, where the pointer may be left over from whatever was planned or tasked last. 2. **Check checklists status** (if FEATURE_DIR/checklists/ exists): - Scan all checklist files in the checklists/ directory - For each checklist, count: - Total items: All lines matching `- [ ]` or `- [X]` or `- [x]` - Completed items: Lines matching `- [X]` or `- [x]` - Incomplete items: Lines matching `- [ ]` - Create a status table: ```text | Checklist | Total | Completed | Incomplete | Status |