Generate QA handoff notes by comparing feature specs against implementation.
npx skills add https://github.com/ricky-yosh/agent-workflows --skill bf-qa-notes
Please help me install this Agent Skill. Skill: bf-qa-notes Source: https://github.com/ricky-yosh/agent-workflows/tree/main/skills/brownfield/bf-qa-notes Command: npx skills add https://github.com/ricky-yosh/agent-workflows --skill bf-qa-notes
Generate concise QA/handoff testing notes after a feature is complete by comparing the spec against the implementation to clearly document what was built, how to test it, and what was intentionally not implemented.
Tell the AI to generate QA notes for the completed feature using the spec and progress context.
High-intent search queries and answers about installing and using this skill.
Generate QA handoff notes by comparing the feature spec against the actual implementation to produce a concise, testable summary. This documents what was built, how to test it, and what was intentionally excluded for downstream reviewers.
QA notes for a brownfield handoff should include a clear enumeration of built features, structured testing steps, identified edge cases, and explicit scope boundaries. This ensures downstream reviewers understand what was implemented and what was left out.
Document release readiness by comparing the spec with the implementation to outline specific testing steps and scope boundaries. This structured test guidance clarifies exactly what downstream QA teams need to validate before release.
Yes, comparing the spec against the implementation identifies and documents what was intentionally not implemented. This process clearly defines scope boundaries so QA teams and stakeholders know exactly what is excluded from the current release.
The best way to create structured test guidance is to automatically compare the completed feature against its spec. This generates a concise summary of built functionalities and specific edge cases for QA teams to verify.
norrbackaGuide project ideas through structured design approval and spec writing.
OmexITCreate risk-based markdown test plans for features, PRs, or releases.
MarkusonParse epic and story markdown to generate sprint-status.yaml tracking files.
DauQuangThanhGenerate API documentation, user guides, tutorials, and technical specifications.
