agentleFS
goodnessibehgoodnessibeh/ai-dev-boilerplate/.claude/skills/qa-test-planner/SKILL.md

qa-test-planner

Skill1 starsChanged 7 months agoNo licenceView on GitHub

Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

13 other projects use a version of this, 6 of them edited; 3 of 6 edited versions we compared changed its rules; 2 new projects in the last 4 weeks, against 1 the 4 before.

How people change it

3 of 6 edited versions changed its rules, and some changes recur.

Of the 6 edited versions we compared: 3 keep every rule, 3 made changes of their own.

Rules people drop

  1. All P0 tests passdropped by 2 of 3
  2. No critical bugs opendropped by 2 of 3
  3. Test one thing per test casedropped by 2 of 3
  4. Use consistent naming conventionsdropped by 2 of 3
  5. Keep test cases maintainabledropped by 2 of 3
  6. Leave expected results vaguedropped by 2 of 3
  7. Run smoke tests frequentlydropped by 2 of 3
  8. Update suite after each releasedropped by 2 of 3

Rules people add

  1. No regression safety netadded by 2 of 3
  2. Test types (functional, UI, performance, etc.)added by 2 of 3
  3. What: Verify features work as specifiedadded by 2 of 3
  4. What: Verify visual appearance and layoutadded by 2 of 3
  5. Verify spacing (padding, margins)added by 2 of 3
  6. Check font sizes and weightsadded by 2 of 3
  7. What: Ensure existing functionality still worksadded by 2 of 3
  8. What: Verify different components work togetheradded by 2 of 3

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Rising: 2 new projects took it in the last 4 weeks, 2× the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 1 new projectWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 1 new projectWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 3 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use agent-md-refactor, game-changing-features and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jeasonstudioSkill

    agent-md-refactor

    Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

    Also in 6 projects that use this

  • wpankSkill

    game-changing-features

    Find 10x product opportunities and high-leverage improvements. Use when the user wants strategic product thinking, mentions 10x, wants to find high-impact features, or asks what would make a product dramatically more valuable.

    Also in 3 projects that use this

  • nahisahoSkill

    database-schema-designer

    Copilot agent for database schema design, ER diagrams, normalization, DDL generation, and performance optimization

    Also in 4 projects that use this

  • eugenepyvovarovSkill

    crafting-effective-readmes

    Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

    Also in 3 projects that use this

  • VercelSkill

    find-skills

    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 10 are common, 0 are distinctive, and 0 are very specific to this project.

  • 10

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.