zcross00
11 verified skills
backlog-entry
BACKLOG ENTRY SKILL — Produce a correctly formatted BL-N backlog entry with all required fields. USE FOR: adding new items to design/BACKLOG.md (features, rework, tech debt, drift items); any role that needs to create a backlog entry. Enforces ID uniqueness and required field completeness. DO NOT USE FOR: updating or removing existing entries (edit directly).
development
build-verify
BUILD VERIFY SKILL — Compile the project and run all tests before committing. USE FOR: pre-commit gate; verifying a fix did not break existing tests; confirming a new test class passes. Provides exact Maven commands, how to read Surefire output, and the pass/fail gate definition. DO NOT USE FOR: writing new tests (use test-writing skill); diagnosing application runtime errors (read source directly).
development
executor-loop
EXECUTOR LOOP SKILL — Pick up the next backlog item, implement it, and deliver. USE FOR: EXECUTOR starting work on the next item; following the correct branch-implement-verify-merge-communicate sequence. Covers the full EXECUTOR cycle from item selection to completion. DO NOT USE FOR: planning or reviewing (PLANNER work); deciding what goes on the backlog (use backlog-entry skill).
development
git-workflow
GIT WORKFLOW SKILL — Exact command sequences for all branch lifecycle operations in this project. USE FOR: creating a work branch for a backlog item; committing and merging work; tagging design versions or releases. Eliminates the need to look up git-workflow.md during implementation. DO NOT USE FOR: deciding what to work on (use backlog-entry or agent-orientation).
testing
planner-review
PLANNER REVIEW SKILL — Review a completed backlog item and update design artifacts accordingly. USE FOR: PLANNER reviewing an EXECUTOR's completed work; updating FEATURES.md after a feature lands; removing completed items from BACKLOG.md; checking for drift. DO NOT USE FOR: implementing backlog items (EXECUTOR work); initial planning (read GOALS and DESIGN directly).
development
standards-check-java
STANDARDS CHECK JAVA SKILL — Apply standards/general.md and standards/java.md systematically to a Java file or diff. USE FOR: pre-commit standards compliance check; reviewing a file for standards adherence before or after a change. Produces a categorized violation list with the specific rule cited for each. DO NOT USE FOR: general code review (use planner-review skill for implementation review).
development
test-writing
TEST WRITING SKILL — Write correctly structured JUnit 5 tests that match this project's conventions. USE FOR: adding tests for a new backlog item; flagging missing test coverage; writing tests for engine classes, domain logic, or persistence. Covers class placement, naming conventions, setup patterns, assertion style, and what not to test. DO NOT USE FOR: running tests (use build-verify skill); diagnosing test failures (read the Surefire report directly).
development
refinement
REFINEMENT SKILL — Analyze design, features, backlog, and drift to identify and plan needed work. USE FOR: PLANNER producing new backlog items from gaps between design and current state; evaluating tech debt and drift for resolution; structured backlog growth when the user asks the PLANNER to refine or plan more work. DO NOT USE FOR: implementing backlog items (EXECUTOR work); reviewing completed work (use planner-review skill).
testing
drift-entry
DRIFT ENTRY SKILL — Log a counter-goal implementation to design/DRIFT.md. USE FOR: any role that identifies an implementation working against a stated goal; adding a new drift item or a new instance to an existing drift item. Enforces the no-duplicate rule and ensures every entry links to a goal. DO NOT USE FOR: resolving drift (create a backlog item instead).
development
domain-model
DOMAIN MODEL SKILL — Decide the correct Java construct for a new domain type and implement it to project conventions. USE FOR: adding a new class, enum, or record; reviewing whether an existing construct is the right type; deciding between mutable JavaBean, record, or enum when the standards are ambiguous. Covers the full decision tree with project-specific examples. DO NOT USE FOR: general Java style checks (use standards-check-java).
development
agent-orientation
ORIENTATION SKILL — Run at the start of every agent session. Reads project artifacts in the correct order, determines the active role per the waterfall, and produces a session brief. USE FOR: starting a new session; determining which role to assume; fast orientation after a gap; confirming project state before picking up work. DO NOT USE FOR: mid-task context checks (read files directly); orientation when the user has explicitly assigned a role (skip waterfall step).
testing