skills.rest
ricky-yosh
ricky-yoshCOMMUNITY
Explore all skills by this author →
GitHub

gf-testing-notes

Generate structured testing notes by comparing feature specs to implemented behavior.

Updated Apr 4, 2026
Search Tags:#testing#documentation#validation#notes#spec#greenfield
One-click install
npx skills add https://github.com/ricky-yosh/agent-workflows --skill gf-testing-notes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gf-testing-notes
Source: https://github.com/ricky-yosh/agent-workflows/tree/main/skills/greenfield/gf-testing-notes
Command: npx skills add https://github.com/ricky-yosh/agent-workflows --skill gf-testing-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate readable testing notes after a feature is complete by comparing the spec to the implementation, producing a concise guide of what was built, how to test it, and any scope gaps.

Core Features & Use Cases

  • Automated spec-vs-implementation comparison to surface gaps and decisions.
  • Structured testing notes including what to test, edge cases, and run instructions.
  • Automatic writing of the final notes to the designated progress folder.

Quick Start

Run the /create-digest step to write the testing notes to .aw/greenfield-progress/testing-notes.md.

Frequently Asked Questions about gf-testing-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate testing notes from a feature spec for a greenfield project?▼

Generate testing notes by running the /create-digest step to compare your feature spec against the implemented behavior, producing a structured testing digest saved to .aw/greenfield-progress/testing-notes.md.

What is the best way to document testing gaps after feature completion?▼

Document testing gaps by comparing the feature spec to the implementation to surface scope gaps and decisions, automatically writing a concise digest of what was built, edge cases, and run instructions to your progress folder.

How does automated spec validation compare to the actual implementation behavior?▼

Automated spec validation compares the feature spec against implemented behavior to identify discrepancies, producing a structured testing digest that includes what to test, edge cases, and scope notes for greenfield projects.

Can I use automated testing digests for existing feature updates instead of just greenfield projects?▼

Automated testing digests apply to greenfield projects and feature completions where you need a test-oriented summary of results, focusing on generating notes from spec-vs-implementation comparisons.

What should a structured testing digest include after a feature is complete?▼

A structured testing digest should include what was built, how to test it, edge cases, run instructions, and scope notes to provide a concise guide of results and decisions after feature completion.

Why do I need to compare my feature spec against the implemented behavior?▼

Comparing your feature spec against implemented behavior surfaces gaps and decisions, allowing you to produce a concise testing guide of what was built and how to test it for feature completions.

Related Skills

Explore More Software Engineering Skills→
SDDKKKSDDKKK

update-spec

Capture executable implementation knowledge into persistent .trellis/spec documents.

Community
Intermediate
lgwanailgwanai
4

gsd-verify-work

Run conversational user acceptance testing and generate phase-specific UAT results.

Community
Intermediate
johan--johan--

reverse-engineer

Generate nine documentation files from code analysis with path selection.

Community
Advanced
olehsvyrydovolehsvyrydov
13

tester

Design test cases and reproduction tests from acceptance criteria.

Community
Intermediate