Day Dream

Blueprint authoring and vision planning for the ADHD Framework.

When to Use

• •Creating a new blueprint (day-dream) plan
• •Authoring feature specs, architecture docs, or implementation plans
• •Building supporting assets (diagrams, data models, mockups)
• •Conceptualizing long-term vision or roadmaps

Tier Selection

Templates are tiered based on project complexity:

Auto-Detection Rules

use_blueprint_tier:
  - feature_count >= 3
  - cross_module_imports >= 2
  - has_external_api: true

Templates Location

All templates at: .agent_plan/day_dream/templates/

Simple Tier

Blueprint Tier

Assets

Asset Types: mockup, diagram, storyboard, infrastructure, design, data-model, other Naming: {feature_id}_{description}.asset.md

Status Syntax

Use hybrid emoji + text markers:

Difficulty Labels

Every feature/task MUST have a difficulty label:

The Story → Spec Pattern

Every blueprint document follows this structure:

## 📖 The Story
{Visual, scannable narrative — NOT a text wall}

---

## 🔧 The Spec
<!-- Technical specification begins here -->

Story Section Requirements (Visual-First for ADHD readers)

Required Subsections:

Why Visual > Text Walls:

• •ADHD readers skip prose, scan visuals
• •ASCII boxes create spatial memory anchors
• •Tables enable instant comparison
• •Emoji provide visual hierarchy

If you can't draw the pain and vision, you don't understand the feature.

Blueprint Document Rules

Mandatory Skeleton Pattern

Rationale: "Optional" is interpreted as "skip if uncertain." Mandatory skeleton forces documentation of decisions.

Template Selection

Index (00_index.md)

• •Progress Overview with emoji status
• •Document navigation table
• •"Where to Start" Mermaid flowchart

Executive Summary (01_executive_summary.md)

• •TL;DR: Maximum 3 sentences
• •Prior Art & Existing Solutions: REQUIRED section
• •Non-Goals: Minimum 3 items
• •Features: Maximum 5 P0 features
• •Freeze after approval with 🔒 FROZEN

Architecture (02_architecture.md)

• •Required when: ≥3 modules OR cross-module deps OR external APIs
• •Key Design Principles table
• •Logical Components: Purpose, Boundary, Implemented By
• •System Diagram: Mermaid, must fit one screen

Implementation (80_implementation.md)

• •YAML frontmatter required
• •P0 Hard Limits: 3-5 days, max 5 tasks, no [RESEARCH]
• •Natural Verification: Every phase MUST have a "How to Verify (Manual)" section
  • •Max 3 human-executable steps
  • •Expected outcome for each step
  • •Steps must complete in <30 seconds

Module Structure (81_module_structure.md)

• •REQUIRED for ADHD projects
• •Defines Reusable vs Project-Specific modules
• •Phase annotations (P0), (P1)

Module Specs (modules/{module_name}.md)

• •Required: ## Implements Features (bidirectional traceability)
• •Links to feature docs that this module serves

Custom Sections (FREE ZONE)

• •Prefix: ## [Custom] 🎨 Title
• •Maximum: 5 custom sections per document
• •Prohibited: P0 tasks, blocking dependencies, architecture changes

Deep Dive Section

Optional for implementation-heavy features:

• •Algorithm Choices, API Contract Draft, Error Handling Strategy
• •Delete if: Straightforward features, obvious implementation

Asset Authoring

Asset Types

Naming Convention

{feature_id}_{description}.asset.md

Required Sections

# {Asset Title}

**Type:** {type}
**Related Feature:** [Feature Title](../blueprint/NN_feature.md)
**Status:** `⏳ [TODO]` | `🔄 [WIP]` | `✅ [DONE]`

## Context
Why this asset exists.

## The Artifact
The actual content: Mermaid diagram, ASCII mockup, etc.

## Constraints
Limitations and assumptions.

## Related Features
Links to dependent features/assets.

Content Guidelines

• •Use Mermaid for diagrams (max: fit one screen)
• •ASCII art for quick mockups
• •Store images in assets/images/ subfolder
• •Prefer SVG over PNG/JPG

Line Limits

Validation Checklists

Feature Checklist

- [ ] The Story section clearly states user problem and value
- [ ] Intent is unambiguous to a non-technical reader
- [ ] Scope is explicitly bounded
- [ ] Integration Points table has all connections
- [ ] Edge Cases cover failure scenarios
- [ ] Acceptance Criteria are testable

Module Checklist

- [ ] Implements Features section links to ≥1 feature OR marked as utility
- [ ] All linked features have backlinks to this module spec
- [ ] Responsibilities clearly state DO and DON'T
- [ ] Public API section defines interface contract

Folder Structure

Simple Tier

.agent_plan/day_dream/
├── {project}_vision.md
└── templates/

Blueprint Tier

.agent_plan/day_dream/
├── blueprint/
│   ├── 00_index.md
│   ├── 01_executive_summary.md
│   ├── 02_architecture.md
│   ├── 03_feature_*.md
│   ├── 80_implementation.md
│   ├── 81_module_structure.md
│   └── modules/
├── assets/
├── exploration/
│   └── _archive/
└── templates/

Anti-Patterns