picobooks

Use to independently review a proposed plan before implementation in Picobooks. Applies when an agent has produced a plan for repository changes and must decide whether there is blocking feedback on intent, scope, constraints, tests, reviewability, or required skills before implementation begins.

Use to independently review completed repository changes before PR creation or update in Picobooks. Applies after implementation and before release to check diffs, tests, constraints, skill adherence, reviewability, and whether blocking feedback remains.

Use when planning/designing, implementing, or reviewing domain code, especially Java/Spring domain and application changes in Picobooks. Applies Domain-Driven Design modeling, Elegant Objects object design, and testability heuristics to keep domain objects behavior-rich, bounded, and easy to unit test.

Use for this repository when planning, reviewing plans, implementing, reviewing implementations, releasing, creating or editing PRs, writing commits, or responding to review comments. Enforces staged plan-review-implement-review delivery, branch-based delivery, Conventional Commit messages and PR titles, short commit bodies, non-draft PRs, local gates, and human review before merge.