Menu
Standards for Technical Specifications (TASK) and Use Cases.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | skill-task-model |
| description | Standards for Technical Specifications (TASK) and Use Cases. |
| tier | 1 |
| version | 1.1 |
Purpose: Defines the structure and quality standards for Technical Specifications to ensure unambiguous implementation.
STOP if you are thinking:
[!TIP] See
examples/good_use_case.mdfor a complete, structured example.
[!TIP] See
examples/bad_use_case.mdfor what NOT to do.
| Agent Excuse | Reality / Counter-Argument |
|---|---|
| "Writing scenarios takes too long" | Rewriting code because of missed edge cases takes 3x longer. |
| "It's obvious what happens" | Obvious to you now. Not obvious to the Code Reviewer or you in 2 weeks. |
examples/: Reference use cases.Use when decomposing tasks into parallel sub-tasks or spawning sub-agents. Vendor-agnostic core; load a per-vendor reference for concrete tool names, directory conventions, and invocation syntax.
Use when performing Verification-Driven Development with adversarial approach. Actively challenge assumptions and find weak spots.
Use when performing VDD adversarial review with an opt-in sarcastic, provocative delivery style — a stylistic skin over vdd-adversarial mechanics (exhaustive reporting + objective bar).
Performance critic in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.
Use when performing OWASP security critique in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.
Use when performing security vulnerability assessment (OWASP, secrets, dependencies, IaC, LLM, API, MCP/agentic) or when "thinking like a hacker" to find exploits.