test-case-table-builder
Skill2 starsChanged 8 months agoMITView on GitHub
In this repository21 other files it gives its agents.
- appendix-assemblerSkill
- architecture-record-writerSkill
- bug-report-writerSkill
- decision-log-writerSkill
- design-rationale-writerSkill
- evaluation-report-writerSkill
- reference-integrity-checkerSkill
- spec-writerSkill
- test-case-table-builderSkill
- test-plan-writerSkill
- traceability-matrix-writerSkill
- appendix-assemblerSkill
- architecture-record-writerSkill
- bug-report-writerSkill
- decision-log-writerSkill
- design-rationale-writerSkill
- evaluation-report-writerSkill
- reference-integrity-checkerSkill
- spec-writerSkill
- test-plan-writerSkill
- traceability-matrix-writerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
Prefer structured, reusable artifacts over generic prose.
- Distinctive: line 55
Do not fabricate evidence, references, or approval.
- Distinctive: line 56
Do not collapse requirements, decisions, tests, and findings into one undifferentiated blob.
- Distinctive: line 57
Do not leave identifiers or document links inconsistent.
- Distinctive: line 58
Do not confuse “described” with “verified”.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
test-case-table-builder
Purpose
Generate test case tables with IDs, preconditions, inputs, expected results, and evidence hooks.
Trigger this skill when
- A durable documentation or evidence artifact is needed for review, submission, audit, or handover.
- You need clearer linkage between requirements, design, testing, defects, decisions, or findings.
- Existing documentation is fragmented, inconsistent, or weakly evidenced.
Expected inputs
- requirements
- scenario list
- expected behaviors
- environment assumptions
Deliverables
- test case table
- coverage notes
- evidence hooks
Operating procedure
- Clarify the artifact boundary, audience, and review objective.
- Separate known facts from assumptions, placeholders, and missing evidence.
- Produce the skill-specific artifact in a form that can be reused directly.
- Link the result to upstream and downstream artifacts where helpful.
- Recommend the next best handoff instead of trying to do every document at once.
Quality gates
- The output is specific to the current system, feature, or report context.
- Identifiers, references, and labels are internally consistent.
- Missing evidence or unresolved questions are made visible.
- The result is directly usable in a repo, report, appendix, or review packet.
Handoff targets
- test-plan-writer
- traceability-matrix-writer
- bug-report-writer
Output style
- Prefer structured, reusable artifacts over generic prose.
- Make IDs, labels, references, and evidence explicit where possible.
- Preserve traceability between related artifacts.
- Surface missing evidence or unresolved questions instead of inventing closure.
Failure modes to avoid
- Do not fabricate evidence, references, or approval.
- Do not collapse requirements, decisions, tests, and findings into one undifferentiated blob.
- Do not leave identifiers or document links inconsistent.
- Do not confuse “described” with “verified”.
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
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.

