// Validates approach and checks assumptions before/after tasks. Use when: starting work, encountering errors, or switching phases.
| name | metacognition |
| description | Validates approach and checks assumptions before/after tasks. Use when: starting work, encountering errors, or switching phases. |
Self-assessment checkpoints.
BLOCKING METACOGNITION REQUIRED at:
ENFORCEMENT: Skipping metacognition = CRITICAL VIOLATION
| Task Type | Essential Rules | Optional Rules |
|---|---|---|
| Implementation | language/rules.md, ai-development-guide.md | architecture patterns |
| Bug Fix | ai-development-guide.md | debugging patterns |
| Design | documentation-criteria.md | architecture patterns |
| Testing | language/testing.md | coverage strategies |
| Refactoring | ai-development-guide.md | design patterns |
Immediate needs: Load only what's required now Progressive loading: Add rules as specific needs arise Cleanup: Unload rules after task completion
Note: Context management is user's responsibility. Ask for guidance if unsure.
☐ [MUST VERIFY] Task type and scale documented with evidence ☐ [MUST VERIFY] Required rules LOADED and file paths listed ☐ [MUST VERIFY] Success criteria MEASURABLE and specific ☐ [MUST VERIFY] Approach validated against existing patterns
GATE: CANNOT start coding if ANY unchecked
☐ [VERIFY] Following Work Plan from docs/plans/
☐ [VERIFY] Making measurable progress (list completed items)
☐ [EVALUATE] Additional rules needed? (load IMMEDIATELY if yes)
☐ [EVALUATE] Blocked for >10 minutes? (MUST ask for help)
Dynamic Rule Loading Triggers:
ai-development-guide.md for debugging patternsENFORCEMENT: If progress stalled → MANDATORY metacognition
☐ [VERIFIED] ALL completion criteria met with evidence ☐ [VERIFIED] Code quality metrics passed (lint, test, build) ☐ [VERIFIED] Documentation updated (if applicable) ☐ [RECORDED] What worked/failed for next iteration
GATE: CANNOT mark complete without ALL verified
| Pattern | Signs | Correction |
|---|---|---|
| Over-engineering | Complex solution for simple problem | Simplify approach |
| Under-planning | Jumping into code too quickly | Step back, plan first |
| Tunnel vision | Ignoring alternatives | Consider other approaches |
| Quality debt | Skipping tests or docs | Complete properly |
| Context bloat | Loading unnecessary rules | Load only essentials |
When stuck:
ERROR HANDLING PROTOCOL:
When encountering an error or blocker:
If unable to resolve:
PRINCIPLE: Ask for help when genuinely stuck, not after arbitrary attempt count
Track:
Remember:
Guides PRD, ADR, Design Doc, and Work Plan creation. Use when: planning features, writing specs, or creating technical documents.
Detects code smells, anti-patterns, and debugging issues. Use when: fixing bugs, reviewing code quality, or refactoring.
Applies coding standards for clean, maintainable code. Use when: writing functions, handling errors, refactoring, or reviewing code style.
Selects implementation strategy (vertical/horizontal/hybrid) with risk assessment. Use when: planning features or deciding development approach.
Designs integration and E2E tests with mock boundaries. Use when: writing E2E tests, integration tests, or reviewing test quality.
Applies TDD process, test quality criteria, and mock guidelines. Use when: writing unit tests, using mocks, or reviewing test quality.