Convert QA matrices or specs into test plans and scenarios.
npx skills add https://github.com/hoonzinope/skills --skill test-author
Please help me install this Agent Skill. Skill: test-author Source: https://github.com/hoonzinope/skills/tree/main/test-author Command: npx skills add https://github.com/hoonzinope/skills --skill test-author
Produce test design artifacts (test plan, scenarios, or skeletons) without writing code, based on QA matrix or specs; write to .documents/qa/TEST_PLAN.md.
Provide a QA matrix or spec and ask the agent to generate a test plan skeleton at the designated path
High-intent search queries and answers about installing and using this skill.
You can generate a QA test plan from a spec without coding by providing a QA matrix or specification to produce a structured Test Plan and Scenarios, which outputs directly to .documents/qa/TEST_PLAN.md.
A manual test plan should include standard sections for Scope, Test Scenarios, Data Sets, Environment, Execution Notes, and Risks, ensuring comprehensive coverage aligned with the product features being tested.
Yes, you can create QA-aligned test scenarios and data sets automatically from a QA matrix, generating ready-to-edit skeletons formatted for team collaboration in your documentation directory.
No coding dependencies are required to produce test design artifacts for manual testing; the process converts your existing specifications into structured test plans and scenarios without any scripting.
The best way to structure test design documents for collaboration is to output ready-to-edit skeletons to a designated target path like .documents/qa/TEST_PLAN.md, conforming to a standard template.
The main limitation is that the output is a ready-to-edit skeleton; while it automatically structures Scope, Scenarios, Data Sets, Environment, Execution Notes, and Risks, you still need to manually refine the content for specific execution contexts.
cenconq25Generate a QA plan document with test types, evidence requirements, and device matrix.
OvidAutomate user acceptance testing with temporary databases and PASS/FAIL reports.
robertbr123Generate markdown project plans and save them in the .linket/plans/ directory.
JoaquinCampoGenerates executable software implementation plans from feature specs.
