Claude Skills by woditschka

The reader board for the handoff log: render each slice of .scratch/handoff.jsonl — header, review-convergence matrix, timeline — to the terminal via scripts/handoff.py view. Load when the user asks where the pipeline stands, for a slice status, or for a review-progress summary. The writer side lives in handoff-append; routing lives in handoff-routing.

Pipeline routing rules and handoff conditions between specialist agents: gates, recovery, and the root-applied procedures. Load when coordinating feature delivery, checking pipeline state, or determining which agent to invoke next. The writer side of the log lives in handoff-append.

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 checklists, threat model, severity classification, and supply chain verification for Go applications. 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, dynamic analysis, and test organization conventions for Go applications. Load when conducting test reviews.

Architecture Decision Record format, naming conventions, and when to create ADRs. Load when making or documenting architectural decisions.

Audit the agentic configuration for consistency, coherence, and conciseness. Load when modifying agent definitions, skills, or pipeline structure, or to verify cross-tool parity.

Audit the project's docs/ briefs against the high bar — each document on its own (principle form, enforceability) and in combination (cross-document coherence, contradictions, brief-vs-data agreement). Runs the doctor (deterministic structural gate) first, then the advisory judgment review, and reports both. Load when you want to check the docs hold up — at onboarding, after a harness upgrade, or on request. The judgment half is advisory: it judges form, never philosophical direction.

Grade a passing change for how much human attention it deserves before merge. Load when running the change-grader after the reviewer roster approves. Holds the full grading protocol: the five facets, worst-facet aggregation, the facets-rationale-verdict order, persistence, and scope/non-goals.

Build, test, format, and lint requirements that must pass before code review. Load when checking implementation completeness or running the quality gate.

Java code quality checklist for Spring Boot applications, plus design placement and workload fit against the project's recorded briefs. Load when conducting code quality reviews.

Draft the project's docs/ briefs by surveying an existing codebase. Recovers requirements, design, vocabulary, and decisions from what the code demonstrably does, marking every statement with how it is known — derived, confirmed, or not recoverable. Load on a brownfield project whose briefs onboarding scaffolded but nobody has written, before the pipeline runs. Not for a greenfield project, where the owner writes them as the work proceeds. Observed behavior is not an intended requirement; thi...

Architectural validation checklist for feature approval. Load when validating that features fit into the existing architecture.

Synchronize documentation with the current codebase. Fix drift between docs/prd.md, docs/system-design.md, and actual source code.

Deterministic, blocking validation of the project's docs/ brief against the harness-project API: roster existence, required sections, data slots, naming conventions, channel invariants, and the reviewer roster. Load when onboarding a project, after a harness upgrade, or before starting pipeline work. Model-free, CI-runnable.

How to write and review project documents: the language-agnostic writing standards, the five-document architecture and ownership boundaries, the document-structure model, cross-reference and maintenance rules, and the review checklist the doc-reviewer enforces. Load when authoring or reviewing any PRD, system-design doc, ADR, brief, or CLAUDE.md.

The writer contract for the handoff log: how every pipeline agent appends records to .scratch/handoff.jsonl through scripts/handoff.py. Load when producing any handoff record — dispatch-start, a substantive record, or a consultation. The routing side lives in handoff-routing.

The reader board for the handoff log: render each slice of .scratch/handoff.jsonl — header, review-convergence matrix, timeline — to the terminal via scripts/handoff.py view. Load when the user asks where the pipeline stands, for a slice status, or for a review-progress summary. The writer side lives in handoff-append; routing lives in handoff-routing.

Pipeline routing rules and handoff conditions between specialist agents: gates, recovery, and the root-applied procedures. Load when coordinating feature delivery, checking pipeline state, or determining which agent to invoke next. The writer side of the log lives in handoff-append.

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.

One-command health check for the IntelliJ IDEA MCP oracle: is it connected, is the right project bound, and is the project model loaded correctly (Gradle imported)? Load when the user asks to check / diagnose / verify the IntelliJ (IDE / MCP / oracle) connection or status, or when an agent is about to rely on the IDE oracle's semantic results and needs to confirm they are trustworthy.

How to use IntelliJ IDEA's MCP tools as a read-only semantic oracle while coding Java/Spring Boot. Use this skill WHENEVER the IntelliJ MCP server is connected and the task involves understanding or validating the codebase — finding where a symbol is used, understanding a type, or checking for problems. Consult it before reaching for grep on a Java question, and after any batch of edits. The agent is the sole writer; IntelliJ never mutates files and never runs code.

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 checklists, threat model, severity classification, and supply chain verification for Java/Spring Boot applications. 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, dynamic analysis, and test organization conventions for Java/Spring Boot applications. Load when conducting test reviews.

Architecture Decision Record format, naming conventions, and when to create ADRs. Load when making or documenting architectural decisions.

Audit the agentic configuration for consistency, coherence, and conciseness. Load when modifying agent definitions, skills, or pipeline structure, or to verify cross-tool parity.

Audit the project's docs/ briefs against the high bar — each document on its own (principle form, enforceability) and in combination (cross-document coherence, contradictions, brief-vs-data agreement). Runs the doctor (deterministic structural gate) first, then the advisory judgment review, and reports both. Load when you want to check the docs hold up — at onboarding, after a harness upgrade, or on request. The judgment half is advisory: it judges form, never philosophical direction.

Grade a passing change for how much human attention it deserves before merge. Load when running the change-grader after the reviewer roster approves. Holds the full grading protocol: the five facets, worst-facet aggregation, the facets-rationale-verdict order, persistence, and scope/non-goals.

Build, test, format, and lint requirements that must pass before code review. Load when checking implementation completeness or running the quality gate.

Code-quality checklist — language-agnostic principles, design placement and workload fit against the project's recorded briefs, and the per-section slots a stack fills in. Load when conducting code quality reviews.

Draft the project's docs/ briefs by surveying an existing codebase. Recovers requirements, design, vocabulary, and decisions from what the code demonstrably does, marking every statement with how it is known — derived, confirmed, or not recoverable. Load on a brownfield project whose briefs onboarding scaffolded but nobody has written, before the pipeline runs. Not for a greenfield project, where the owner writes them as the work proceeds. Observed behavior is not an intended requirement; thi...

Architectural validation checklist for feature approval. Load when validating that features fit into the existing architecture.

Synchronize documentation with the current codebase. Fix drift between docs/prd.md, docs/system-design.md, and actual source code.

Deterministic, blocking validation of the project's docs/ brief against the harness-project API: roster existence, required sections, data slots, naming conventions, channel invariants, and the reviewer roster. Load when onboarding a project, after a harness upgrade, or before starting pipeline work. Model-free, CI-runnable.

How to write and review project documents: the language-agnostic writing standards, the five-document architecture and ownership boundaries, the document-structure model, cross-reference and maintenance rules, and the review checklist the doc-reviewer enforces. Load when authoring or reviewing any PRD, system-design doc, ADR, brief, or CLAUDE.md.

The writer contract for the handoff log: how every pipeline agent appends records to .scratch/handoff.jsonl through scripts/handoff.py. Load when producing any handoff record — dispatch-start, a substantive record, or a consultation. The routing side lives in handoff-routing.

The reader board for the handoff log: render each slice of .scratch/handoff.jsonl — header, review-convergence matrix, timeline — to the terminal via scripts/handoff.py view. Load when the user asks where the pipeline stands, for a slice status, or for a review-progress summary. The writer side lives in handoff-append; routing lives in handoff-routing.

Pipeline routing rules and handoff conditions between specialist agents: gates, recovery, and the root-applied procedures. Load when coordinating feature delivery, checking pipeline state, or determining which agent to invoke next. The writer side of the log lives in handoff-append.