the-own-lab/test-plan
skills/test-plan/SKILL.md
Decide WHAT to test before writing tests. Output: golden / edge / error / won't-test. Feeds tdd.
development
Updated Apr 22, 2026
$ install --global
skillsauthnpx skillsauth add the-own-lab/Claude-company-of-one test-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 11:19 AM167.5s1 file scanned
SKILL.md
- name:
- test-plan
- description:
- Decide WHAT to test before writing tests. Output: golden / edge / error / won't-test. Feeds tdd.
test-plan
Purpose
Pre-code step in /dev. Partition the coverage space into four buckets so tdd
knows which tests to write. "Won't test" is mandatory — the explicit boundary
prevents both overtesting and silent gaps.
Inputs
BRIEF.md## Current Contract,### Requirements Summary,### Design Summary,### TODO In Scope, and## Human-Owned Core(already populated byexplain-60-40earlier in/dev).- Do NOT re-read REQUIREMENTS.md / DESIGN.md directly. The brief is the contract.
Outputs
- Appended block in
BRIEF.md:
## Test Plan
### Golden path
- ...
### Edge cases
- ...
### Error paths
- ...
### Won't test (and why)
- ...
Procedure
- Golden path first. If it is unclear, the feature is not ready — route back to
clarify. - Edge cases: boundary, empty, max, concurrency, malformed input. Cap at 5. More than 5 = too many modes in one feature; split it.
- Error paths: for each expected failure mode, describe the error the user sees.
- Won't test: for each deliberate omission, cite the reason (covered-by-types / trivial / integration-tested-elsewhere / 60%-boilerplate).
- Name tests by behavior, not by function:
it_sends_email_on_signup.
Failure modes
- Empty
Won't test→ incomplete plan. Boundary must be explicit. - Edge-case count > 5 → scope signal; push back to
spec-writingbefore continuing. - Planning > 10 tests total for one feature → feature is too big.
Does not do
- Does not write tests (that is
tdd). - Does not run tests (that is
verify). - Does not substitute for
tdd's RED step; planning a test is not writing it.
Related Skills
the-own-lab/write-brief
documentation
VerifiedTrustedCommunity
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/verify
development
VerifiedTrustedCommunity
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/update-docs
documentation
VerifiedTrustedCommunity
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/spec-writing
content-media
VerifiedTrustedCommunity
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.
SKILL.mdUpdated Apr 22, 2026