ricky-yosh
25 verified skills
ex-triage
Example skill — pick the next task and write next-task.json. Demonstrates task selection with AskUserQuestion and skip_when output.
documentation
bf-resume
Resume work on a ticket by loading context from .aw/brownfield-progress/ files. Reads research.txt, tasks.json, progress.txt, and recent git log to summarize where you left off and suggest next steps. Part of the brownfield skill family. Use when the user says /bf-resume, wants to pick up where they left off, or starts a new session on a ticket.
research
bf-create-tasks
Generate a structured task list (tasks.json) for a ticket from an existing spec. Reads spec.txt from .aw/brownfield-progress/ and writes tasks.json in the same directory. Part of the brownfield skill family. Use when the user says /bf-create-tasks, wants to break down a spec into actionable tasks, or needs a task list to track implementation progress.
documentation
bf-implement
Execute the approved plan for the current task and produce an implementation digest. Reads next-task.json, implements the plan, then invokes /create-digest to write implement-task-N-digest.md with what changed and how to verify. Part of the brownfield skill family.
testing
bf-qa-notes
Generate QA/handoff testing notes after a feature is complete. Compares spec against implementation to draft precise, concise notes — what was built, how to test it, and what was intentionally not implemented. Part of the brownfield skill family. Use when the user says /bf-qa-notes, 'write QA notes', or is handing off a completed feature.
testing
bf-triage
Pick the next task to work on and write it to next-task.json. Reads tasks.json, selects the first not-done task, confirms with the user, and persists the choice. Part of the brownfield skill family. Use when the user says /bf-triage, 'what should I work on next', 'which task is next', or as the step between /bf-resume and /bf-plan.
documentation
create-digest
Distill a document into a tight, journalist-style digest. Use when the user wants a summary, digest, or readable version of any document — specs, research notes, meeting transcripts, technical docs, PRDs, RFCs, or anything verbose that needs to be made concise and human. Also use when the user says /create-digest or asks to 'make this readable' or 'give me the highlights'.
testing
ex-save-progress
Example skill — mark current task done and write progress.json + tasks.json. Demonstrates multi-output completion detection.
documentation
gf-create-git-commits
Creates well-structured git commits from current changes. Analyzes staged or unstaged changes and splits them into coherent logical commits grouped by intention. Part of the gf (greenfield) skill family. Use when the user says /gf-create-git-commits, asks to commit their work, or wants to save progress as git commits during a long feature build.
development
gf-create-tasks
Generate a structured task list (tasks.json) from an existing spec. Tasks follow the walking skeleton philosophy — Task 1 builds the thinnest end-to-end system, each subsequent task replaces a hardcoded seam with real functionality. Writes to .aw/greenfield-progress/tasks.json. Part of the gf (greenfield) skill family.
development
gf-resume
Resume work on a long feature by loading context from .aw/greenfield-progress/ files. Reads spec.xml, tasks.json, progress.txt, and recent git log to summarize where you left off. Writes next-task.json for the next not-done task. Part of the gf (greenfield) skill family.
documentation
gf-save-progress
Save current session work to .aw/greenfield-progress/progress.txt. Captures decisions (why, not just what) that git diff cannot show. Updates tasks.json to mark completed tasks. Part of the gf (greenfield) skill family.
testing
gf-write-tests
Write tests for a batch of tasks BEFORE implementation. Detects the project's test framework and language, then writes tests that cover happy paths, edge cases, and failure modes. All tests should fail initially since there is no implementation yet. Part of the gf (greenfield) skill family. Use when the user says /gf-write-tests or wants to write tests before implementing a feature or task batch.
development
bf-create-tests
Write tests for a batch of tasks BEFORE implementation. Detects the project's test framework and conventions, then writes tests covering happy paths, edge cases, and failure modes. All tests should fail initially since there's no implementation yet. Part of the brownfield skill family. Use when the user says /bf-create-tests or wants to write tests before implementing a task batch.
development
bf-create-spec
Collaboratively build an implementation spec. Asks the user what they want to build, interviews them to clarify scope and constraints, and writes spec.txt (including research hints for bf-research). Part of the brownfield skill family.
development
bf-research
Research how an area of the codebase works. Reads spec.txt for the goal and research hints, explores the relevant code, and writes research.txt. Part of the brownfield skill family. Use when the user says /bf-research or wants to understand a codebase area before implementation.
development
bf-plan
Create an implementation plan for a batch of tasks using Claude Code Plan mode. Reads research.txt, spec.txt, and tasks.json, identifies the established patterns in the target area, and enters Plan mode with that context injected. Ensures the plan follows the codebase's existing architecture. Part of the brownfield skill family. Use when the user says /bf-plan or wants to plan a batch of tasks before implementing.
development
ex-create-spec
Example skill — write a spec from a one-line idea. Demonstrates AskUserQuestion input, .draft file pattern, and digest output.
documentation
bf-save-progress
Save current session work to .aw/brownfield-progress/progress.txt in the current worktree. Captures decisions (why, not just what) that git diff cannot show. Part of the brownfield skill family. Use when the user says /bf-save-progress, wants to capture session state, or is wrapping up work on a ticket.
testing
review-implementation
Ask the user to verify the implementation before advancing. Reads the implementation digest and presents verification steps, then gates on user confirmation. Writes review-confirmed marker file only after the user approves. Generic skill shared across all workflow families.
testing
gf-plan
Research the task, form a recommended approach, ask the user to confirm or redirect via AskUserQuestion, then enter Plan mode. Part of the gf (greenfield) skill family.
research
gf-implement
Implement the current task from next-task.json directly — no plan mode. Reads the task, writes tests if needed, implements, and verifies. Use for tasks marked 'direct'. Part of the gf (greenfield) skill family. Use when the user says /gf-implement.
testing
gf-create-spec
Collaboratively brainstorm and build a feature specification. Acts as a thinking partner — listens to the user's braindump, asks smart follow-ups, then crystallizes everything into spec.xml. Part of the gf (greenfield) skill family.
development
gf-testing-notes
Generate readable testing notes after a feature is complete. Compares spec against implementation to produce a concise list of what was built, how to test it, and any scope gaps. Writes testing-notes.md to .aw/greenfield-progress/. Part of the gf (greenfield) skill family.
testing
gf-review
Gate the greenfield workflow on user verification after an implementation step. Reads the implementation digest, shows verification steps, and waits for the user to confirm before advancing. Part of the gf (greenfield) skill family.
testing