ricky-yosh/gf-write-tests
skills/greenfield/gf-write-tests/SKILL.md
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
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add ricky-yosh/agent-workflows gf-write-testsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 8:39 PM31.2s1 file scanned
SKILL.md
- name:
- gf-write-tests
- description:
- 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.
- model:
- opus
Write Tests (Long Feature)
Write tests for a batch of tasks before implementation. Tests define the contract; implementation satisfies it later. Do not ask unnecessary questions — read the inputs, make decisions, and write the tests.
Steps
-
Read
.aw/greenfield-progress/spec.xmland.aw/greenfield-progress/tasks.json. If either is missing, tell the user which skill to run first and stop. -
Pick the target tasks. Read
.aw/greenfield-progress/next-task.json. If it exists, use that task — no confirmation needed (resume already selected it). If it doesn't exist, ask which tasks to target. Accept task numbers (e.g., "tasks 2-4") or "all remaining". -
Skip if tests don't make sense. Tasks that are purely UI layout, config wiring, file reorganization, docs, or copy changes don't need tests. If the selected task has no testable logic, say so in one line and stop. Otherwise proceed — no announcement needed.
-
Detect the project's test setup. Find test framework config, existing test files, and their patterns (naming, imports, assertion style). If no test setup exists, ask the user what framework to use. Read existing tests and the source files relevant to the task so you understand the interfaces being tested.
-
Write the tests. Tests must:
- Follow the project's existing test conventions exactly
- Cover happy paths, edge cases, and failure modes
- Use strict assertions —
assertEqual(result, 42)notassertNotNone(result) - Reference interfaces/functions that don't exist yet — that's the point
- Not include any implementation code
-
End with a summary table:
| Category | Coverage | Count | |---|---|---:| | Happy path | ... | N | | Edge cases | ... | N | | Error handling | ... | N | | Total | | N |
-
Iterate until approved.
Principles
- Tests are the spec made executable. Each acceptance criterion from spec.xml should map to at least one test.
- Strict assertions. Loose assertions hide bugs.
- No implementation code. Tests define the contract; implementation satisfies it later.
Related Skills
ricky-yosh/gf-testing-notes
testing
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 16, 2026
ricky-yosh/gf-save-progress
testing
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 16, 2026
ricky-yosh/gf-review
testing
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 16, 2026
ricky-yosh/gf-resume
documentation
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 16, 2026