skills/brownfield/bf-research/SKILL.md
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.
npx skillsauth add ricky-yosh/agent-workflows bf-researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Explore an area of the codebase and document how it works.
Read .aw/brownfield-progress/spec.txt — if missing, tell the user to run /bf-create-spec first. Use the Goal section to understand what's being built and the Research Hints section as starting points for exploration. If Research Hints is blank, infer starting points from the goal and scope.
Starting from the files and modules listed, explore the relevant code. Trace through the layers of the feature area — from entry points (UI, CLI, API handlers) through business logic to data storage. Focus on the layers where the feature's core logic lives; skip shared infrastructure or low-level plumbing that doesn't vary between features.
Document what's relevant from:
Write .aw/brownfield-progress/research.txt.draft. Include the sections that are relevant to the area — not every section applies to every feature. Area Overview, Key Files, and Observations should always be included. The rest are optional.
# Research: [Feature Area]
## Area Overview
[What this part of the codebase does and how it's structured]
## Key Files
[Most relevant files with a one-line description of each]
## Data Flow
[How data moves through this area — source to display/output]
## Patterns in Use
[Patterns that appear consistently in nearby code]
## Observations
[Anything surprising or worth noting]
Present the findings to the user for review using AskUserQuestion:
AskUserQuestion:
question: "Here's the research. Does it look right?"
options:
- "Approved"
- "Dig deeper into something"
- "Something's missing"
If anything other than "Approved", use a follow-up AskUserQuestion to find out what. Explore further, update the .draft file, and re-present until approved.
Once approved:
.aw/brownfield-progress/research.txt.draft to .aw/brownfield-progress/research.txt..aw/digests/research-digest.md — see /create-digest for voice and structure..aw/brownfield-progress/research.txt. Digest at .aw/digests/research-digest.md"development
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.
testing
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
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
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.