do-task
Do Task
Overview
Implement a specific action item from docs/ROADMAP.md by its ID. Read the task's full context from the roadmap, research as needed, clarify ambiguities with the user, execute the implementation, and deliver a test plan.
Workflow
Step 1: Parse and Load Task
Extract the task ID from the user's arguments (e.g., 1.1, 2.3, 3.1).
Read docs/ROADMAP.md from the current working directory. If the file does not exist, check for ROADMAP.md at the project root. If neither exists, inform the user and stop.
Locate the action item matching the given ID (the ### X.Y heading). Extract:
More from b-j-roberts/vibecoding-workshop
scope-task
This skill scopes and researches a single new task to insert into an existing project's ROADMAP.md. It should be used when a developer identifies a gap in the roadmap during the do-task/checkpoint loop and needs to properly scope a new action item before implementing it. Triggered by requests like '/scope-task 2.5 Integrate Research into SPEC.md', '/scope-task 3.3 Add WebSocket support', or 'scope task 1.4 Set up CI pipeline'. Works alongside project-init (which creates the roadmap) and do-task (which implements tasks).
14project-init
This skill initializes new software projects through a structured discovery, research, and documentation workflow. It should be used when the user wants to create/initialize a new project, start a new app, scaffold a new codebase, or plan a new software product. Triggered by requests like 'create a new project', 'initialize a new app', 'start a new project for X', 'I want to build X'. The skill does NOT generate code — it produces a project directory with comprehensive documentation (SPEC.md, STYLES.md, ROADMAP.md) that serves as the blueprint for implementation.
13checkpoint
Review local git changes and perform a light code review. If no issues are found, commit the changes. Does NOT write or modify code — only reviews and commits. Optionally accepts a commit message header as an argument.
13