testcase-writer-plus
- Repo stars 74
- Author updated Live
- Author repo awesome-qa-skills
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @naodeng · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Shell exec
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: testcase-writer-plus
description: Parse requirement and analysis files, then generate high-quality test cases. Markdown by default…
category: engineering
runtime: no special runtime
---
# testcase-writer-plus output preview
## PART A: Task fit
- Use case: Parse requirement and analysis files, then generate high-quality test cases. Markdown by default unless the request explicitly asks for another format. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use / Output Format Options / How to Use” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Parse requirement and analysis files, then generate high-quality test cases. Markdown by default unless the request explicitly asks for another format. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “When to Use / Output Format Options / How to Use” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, run shell commands, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “When to Use / Output Format Options / How to Use”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: testcase-writer-plus
description: Parse requirement and analysis files, then generate high-quality test cases. Markdown by default…
category: engineering
source: naodeng/awesome-qa-skills
---
# testcase-writer-plus
## When to use
- Parse requirement and analysis files, then generate high-quality test cases. Markdown by default unless the request ex…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Use / Output Format Options / How to Use” and keep inference separate from source facts.
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "testcase-writer-plus" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Use / Output Format Options / How to Use
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, run shell commands, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}testcase-writer-plus (EN)
中文版： 见对应中文技能。
When to Use
- Need test cases from multiple source documents with stronger prioritization.
- Need better traceability and clearer risk focus than the base version.
Output Format Options
Markdown by default unless the request explicitly asks for another format.
How to Use
- Open
prompts/testcase-writer-plus.mdand use it as the main prompt. - Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
- If the input is incomplete, return a usable first version and mark missing information and assumptions.
Reference Files
prompts/testcase-writer-plus.md: main prompt for this skill.references/: supporting notes loaded only when needed.examples/: sample inputs or outputs.scripts/: helper scripts or converters for this skill.
Common Pitfalls
- Do not use it with vague scope and no context.
- Do not treat every area as equally important.
- Do not skip assumptions and missing information.
Best Practices
- Start from the prompt file, then add only the context that matters.
- Keep the output risk-driven and executable.
- If the request is incomplete, return a usable first version and mark gaps.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review