shinpr/agentic-code — Prompts
Prompt 1: AGENTS.md — Plan Injection (verbatim)
Source: .agents/tasks/AGENTS.md (the root AGENTS.md)
## Plan Injection [MANDATORY ENFORCEMENT]
**All tasks require Plan Injection for BLOCKING READs:**
- Task-analysis.md Step 8 scans and identifies ALL BLOCKING READ requirements
- Work plans MUST contain every BLOCKING READ from workflow/tasks/skills
- Each phase verifies its BLOCKING READs are in the plan
- Gates verify Plan Injection evidence before proceeding
- Missing ANY BLOCKING READ = IMMEDIATE HALT
Prompting technique: Hard constraint with automatic halt condition. The "IMMEDIATE HALT" language is an explicit behavioral override that takes precedence over any competing instruction. This is more aggressive than superpowers' "Iron Law" pattern because it creates a specific error state (halt + return to task analysis) rather than just forbidding the behavior.
Prompt 2: implementation.md — Entry Gate (verbatim)
Source: .agents/tasks/implementation.md
## Phase Entry Gate [BLOCKING - SYSTEM HALT IF VIOLATED]
**CHECKPOINT: System CANNOT write ANY CODE until ALL boxes checked:**
☐ [VERIFIED] THIS FILE (`implementation.md`) has been READ and is active
☐ [VERIFIED] Task Tracking completed (from implementation.md Task Tracking Requirement)
☐ [VERIFIED] All required rules listed above are LOADED and active
☐ [VERIFIED] Work Plan document EXISTS with task definitions
☐ [VERIFIED] Task List contains ALL BLOCKING READs from this file
☐ [VERIFIED] Current task identified from Work Plan document
☐ [VERIFIED] TDD process understood (Red-Green-Refactor-Verify)
☐ [VERIFIED] SESSION_BASELINE_DATE established and active
**METACOGNITION GATE [MANDATORY]:**
BEFORE writing first line of code:
- Understand what needs to be built
- Verify approach follows existing patterns
- Confirm TDD cycle will be followed
Prompting technique: Checkbox verification list as a hard gate. The agent must produce explicit evidence (the filled checkboxes) before proceeding. This pattern makes the pre-condition verification visible in the output rather than implicit.
Source: AGENTS.md
## Metacognition Checkpoints
Perform self-assessment at these mandatory points:
- Task type changes
- Unexpected errors occur
- Completing a meaningful unit of work
- Before starting new implementation
- After completing each task from work plan
Prompting technique: Mandatory self-monitoring injection at session start. The metacognition skill is the only skill that is required to remain active for the entire session (not unloaded after its task phase completes). This acts as a persistent meta-layer monitoring all other behavior.