brmatola
Publisher on askill
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use after implementing a plan to verify completeness, correctness, and merge safety - the post-implementation gate
Use when executing implementation plans with independent tasks in the current session
Use when you have a plan with trellis chunks and want to pressure-test whether a chunk represents a cohesive, buildable featureset before implementation
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence...
Use after implementing a plan to verify completeness, correctness, and merge safety - the post-implementation gate
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent and contracts, and mandatory freshness date...
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verificat...
Use when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent and contracts, and mandatory freshness date...
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence...
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when you have a written implementation plan to execute - runs autonomously by default, or in batched mode with checkpoints
Showing 18 of 19