Claude Skills by woditschka

Run slice intake as a live discussion under the product expert's contract, then record the owner's request and decisions verbatim as an intake-decision record. Load when the user brings a feature request for discussion or invokes /intake.

Clear the scratch directory and start a fresh feature context. Load when starting a new feature or resetting pipeline state.

Reset feature context and recommend what to work on next based on PRD coverage. Load when the user asks "what's next" or invokes /next.

PRD format conventions, boundary rules, and template references. Load when writing or reviewing product requirements.

Review process overview, feedback tag definitions, and output format. Load when conducting or processing code reviews.

Security-review checklist, threat model, severity classification, and supply chain verification — language-agnostic, with per-section slots a stack fills in. Load when conducting security reviews.

Run the quality gate, then commit staged and unstaged changes and push to the remote in one step. Load when the user asks to commit and push, or invokes /ship.

TDD cycle process and design-check decision tree for feature implementation. Load when implementing features using test-driven development.

Test quality checklist, security-testing requirements, and dynamic-analysis expectations — language-agnostic, with per-section slots a stack fills in. Load when conducting test reviews.

Generate a per-agent cache-efficiency report for the current Claude Code session. Use when the user asks about cache stats, cache efficiency, prompt-cache performance, token savings, or whether subagents are using cache effectively. Examples: "show cache report", "how's the cache doing", "cache stats", "are subagents efficient", "which agents are wasting cache", "session token breakdown".