[IDEA GOES HERE]
Populate this template:
# TASK
Work strictly BACKWARDS from my vision to construct an actionable, dependency-driven execution blueprint.
# INPUTS
- IDEAL STATE: [What does success look like when 100% complete?]
- CURRENT STATE: [Where do things stand right now?]
- CONSTRAINTS: [Non-negotiable limits on time, budget, tools, or scope]
# REVERSE LOGIC
1. Completion Criteria: Define 2-3 objective, verifiable artifacts that prove this is complete.
2. Final Gate (N-1): What single output or condition MUST exist immediately prior to completion?
3. Core Driver (N-2): What underlying asset or setup enables that final gate?
4. Fatal Flaw Premortem: What is the most likely friction point between the current baseline and Step 3, and how is it bypassed?
5. Day 1 Unlock: What single action must happen today to enable everything else?
# FORWARD EXECUTION BLUEPRINT
Convert the reverse logic into a chronological action sequence. For each step, define the specific ARTIFACT produced:
- Step 1 (Immediate Unlock) -> [Artifact/Output]
- Step 2 (Core Build) -> [Artifact/Output]
- Step 3 (Final Gate) -> [Artifact/Output]