testcase writer plus

Engineering Community

Skill notes

When to Use

Need test cases from multiple source documents with stronger prioritization. Need better traceability and clearer risk focus than the base version.

How to Use

Open prompts/testcase-writer-plus.md and 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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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 explicit requirements detected
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# 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

1. Open `prompts/testcase-writer-plus.md` and use it as the main prompt.
2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
3. 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.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.