kk

Apply Chain-of-Verification (CoVe) with true factored verification using isolated sub-agents.

Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification.

Verify implemented code against design and implementation documentation, detecting spec deviations, missing implementations, and outdated docs.

Run implementation review in isolated mode with an independent spec-reviewer sub-agent that has zero authorship bias.

Migrate this project from Task Master MCP to native markdown-based task tracking.

Run SOLID code review in isolated mode with independent sub-agents that have zero authorship bias.

Update the local template-sync workflow and script from the upstream template repository.

Independent code reviewer with no authorship attachment. Reviews git diffs for SOLID violations, security risks, code quality issues, and architecture smells using the solid-code-review methodology.

Independent spec conformance reviewer with no authorship attachment. Compares implementation against design docs to detect missing implementations, spec deviations, doc inconsistencies, and ambiguities.

Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/wip/.

Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.

Use when writing code to ensure you follow development best practices during development and implementation.

After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.

TRIGGER when: user asks to work on, implement, or continue tasks from docs/wip (e.g. "work on task 1", "do the next task", "implement first task for X"). Executes written implementation plans with review checkpoints. Use when you have a fully-formed implementation plan to execute in a separate session.

Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.

Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate analysis-process runs) that need reconciling into one unified document.

Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.

Guidelines describing how to test the code. Use whenever writing new or updating existing code, for example after implementing a new feature or fixing a bug.

1 hook across 1 event