@tgoodington/intuition 11.4.0 → 11.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (131) hide show
  1. package/package.json +1 -2
  2. package/skills/intuition-enuncia-compose/SKILL.md +5 -10
  3. package/skills/intuition-enuncia-design/SKILL.md +0 -4
  4. package/skills/intuition-enuncia-discovery/SKILL.md +1 -7
  5. package/skills/intuition-enuncia-execute/SKILL.md +0 -4
  6. package/skills/intuition-enuncia-handoff/SKILL.md +0 -4
  7. package/skills/intuition-enuncia-initialize/references/claude_template.md +20 -0
  8. package/skills/intuition-enuncia-start/SKILL.md +0 -4
  9. package/skills/intuition-enuncia-verify/SKILL.md +0 -4
  10. package/docs/archive/ARCHITECTURE_OVERVIEW.txt +0 -405
  11. package/docs/archive/INSTALLATION.md +0 -431
  12. package/docs/archive/PROJECT_CONTEXT.md +0 -361
  13. package/docs/archive/QUICK_TEST_CHECKLIST.md +0 -467
  14. package/docs/archive/SKILL_INTERACTION_GUIDE.md +0 -993
  15. package/docs/archive/TESTING_README.md +0 -215
  16. package/docs/archive/TESTING_SUMMARY.md +0 -781
  17. package/docs/archive/WALDO_V3_COMPLETE_DOCUMENTATION.md +0 -538
  18. package/docs/archive/WALDO_V3_DESIGN_SUMMARY.md +0 -449
  19. package/docs/archive/intuition-architecture.md +0 -342
  20. package/docs/archive/intuition-workflow.md +0 -210
  21. package/docs/archive/intuition_design_skill_spec.md +0 -219
  22. package/docs/archive/v7_design_spec.md +0 -1111
  23. package/docs/archive/v7_plan.md +0 -339
  24. package/docs/archive/v9-design/decision-framework-direction.md +0 -142
  25. package/docs/archive/v9-design/decision-framework-implementation.md +0 -114
  26. package/docs/archive/v9-design/domain-adaptive-team-architecture.md +0 -1016
  27. package/docs/archive/v9-test/SESSION_SUMMARY.md +0 -117
  28. package/docs/archive/v9-test/TEST_PLAN.md +0 -119
  29. package/docs/archive/v9-test/blueprints/legal-analyst.md +0 -166
  30. package/docs/archive/v9-test/output/07_cover_letter.md +0 -41
  31. package/docs/archive/v9-test/phase2/mock_plan.md +0 -89
  32. package/docs/archive/v9-test/phase2/producers.json +0 -32
  33. package/docs/archive/v9-test/phase2/specialists/database-architect.specialist.md +0 -10
  34. package/docs/archive/v9-test/phase2/specialists/financial-analyst.specialist.md +0 -10
  35. package/docs/archive/v9-test/phase2/specialists/legal-analyst.specialist.md +0 -10
  36. package/docs/archive/v9-test/phase2/specialists/technical-writer.specialist.md +0 -10
  37. package/docs/archive/v9-test/phase2/team_assignment.json +0 -61
  38. package/docs/archive/v9-test/phase3/blueprints/legal-analyst.md +0 -840
  39. package/docs/archive/v9-test/phase3/legal-analyst-full.specialist.md +0 -111
  40. package/docs/archive/v9-test/phase3/project_context/nh_landlord_tenant_notes.md +0 -35
  41. package/docs/archive/v9-test/phase3/project_context/property_facts.md +0 -32
  42. package/docs/archive/v9-test/phase3b/blueprints/legal-analyst.md +0 -1715
  43. package/docs/archive/v9-test/phase3b/legal-analyst.specialist.md +0 -153
  44. package/docs/archive/v9-test/phase3b/scratch/legal-analyst-stage1.md +0 -270
  45. package/docs/archive/v9-test/phase4/TEST_PLAN.md +0 -32
  46. package/docs/archive/v9-test/phase4/blueprints/financial-analyst-T2.md +0 -538
  47. package/docs/archive/v9-test/phase4/blueprints/legal-analyst-T4.md +0 -253
  48. package/docs/archive/v9-test/phase4/cross-blueprint-check.md +0 -280
  49. package/docs/archive/v9-test/phase4/scratch/financial-analyst-T2-stage1.md +0 -67
  50. package/docs/archive/v9-test/phase4/scratch/legal-analyst-T4-stage1.md +0 -54
  51. package/docs/archive/v9-test/phase4/specialists/financial-analyst.specialist.md +0 -156
  52. package/docs/archive/v9-test/phase4/specialists/legal-analyst.specialist.md +0 -153
  53. package/docs/archive/v9-test/phase5/TEST_PLAN.md +0 -35
  54. package/docs/archive/v9-test/phase5/blueprints/code-architect-hw-vetter.md +0 -375
  55. package/docs/archive/v9-test/phase5/output/04_compliance_checklist.md +0 -149
  56. package/docs/archive/v9-test/phase5/output/hardware-vetter-SKILL-v2.md +0 -561
  57. package/docs/archive/v9-test/phase5/output/hardware-vetter-SKILL.md +0 -459
  58. package/docs/archive/v9-test/phase5/producers/code-writer.producer.md +0 -49
  59. package/docs/archive/v9-test/phase5/producers/document-writer.producer.md +0 -62
  60. package/docs/archive/v9-test/phase5/regression-comparison-v2.md +0 -60
  61. package/docs/archive/v9-test/phase5/regression-comparison.md +0 -197
  62. package/docs/archive/v9-test/phase5/review-5A-specialist.md +0 -213
  63. package/docs/archive/v9-test/phase5/specialist-test/TEST_PLAN.md +0 -60
  64. package/docs/archive/v9-test/phase5/specialist-test/blueprint-comparison.md +0 -252
  65. package/docs/archive/v9-test/phase5/specialist-test/blueprints/code-architect-hw-vetter.md +0 -916
  66. package/docs/archive/v9-test/phase5/specialist-test/scratch/code-architect-stage1.md +0 -427
  67. package/docs/archive/v9-test/phase5/specialists/code-architect.specialist.md +0 -168
  68. package/docs/archive/v9-test/phase5b/TEST_PLAN.md +0 -219
  69. package/docs/archive/v9-test/phase5b/blueprints/5B-10-stage2-with-decisions.md +0 -286
  70. package/docs/archive/v9-test/phase5b/decisions/5B-2-accept-all-decisions.json +0 -68
  71. package/docs/archive/v9-test/phase5b/decisions/5B-3-promote-decisions.json +0 -70
  72. package/docs/archive/v9-test/phase5b/decisions/5B-4-individual-decisions.json +0 -68
  73. package/docs/archive/v9-test/phase5b/decisions/5B-5-triage-decisions.json +0 -110
  74. package/docs/archive/v9-test/phase5b/decisions/5B-6-fallback-decisions.json +0 -40
  75. package/docs/archive/v9-test/phase5b/decisions/5B-8-partial-decisions.json +0 -46
  76. package/docs/archive/v9-test/phase5b/decisions/5B-9-complete-decisions.json +0 -54
  77. package/docs/archive/v9-test/phase5b/scratch/code-architect-stage1.md +0 -133
  78. package/docs/archive/v9-test/phase5b/specialists/code-architect.specialist.md +0 -202
  79. package/docs/archive/v9-test/phase5b/stage1-many-decisions.md +0 -139
  80. package/docs/archive/v9-test/phase5b/stage1-no-assumptions.md +0 -70
  81. package/docs/archive/v9-test/phase5b/stage1-with-assumptions.md +0 -86
  82. package/docs/archive/v9-test/phase5b/test-5B-1-results.md +0 -157
  83. package/docs/archive/v9-test/phase5b/test-5B-10-results.md +0 -130
  84. package/docs/archive/v9-test/phase5b/test-5B-2-results.md +0 -75
  85. package/docs/archive/v9-test/phase5b/test-5B-3-results.md +0 -104
  86. package/docs/archive/v9-test/phase5b/test-5B-4-results.md +0 -114
  87. package/docs/archive/v9-test/phase5b/test-5B-5-results.md +0 -126
  88. package/docs/archive/v9-test/phase5b/test-5B-6-results.md +0 -60
  89. package/docs/archive/v9-test/phase5b/test-5B-7-results.md +0 -141
  90. package/docs/archive/v9-test/phase5b/test-5B-8-results.md +0 -115
  91. package/docs/archive/v9-test/phase5b/test-5B-9-results.md +0 -76
  92. package/docs/archive/v9-test/producers/document-writer.producer.md +0 -62
  93. package/docs/archive/v9-test/specialists/legal-analyst.specialist.md +0 -58
  94. package/docs/project_notes/.project-memory-state.json +0 -100
  95. package/docs/project_notes/archive/trunk-v9.2-complete/.gitkeep +0 -0
  96. package/docs/project_notes/archive/trunk-v9.2-complete/.planning_research/decision_file_naming.md +0 -15
  97. package/docs/project_notes/archive/trunk-v9.2-complete/.planning_research/decisions_log.md +0 -32
  98. package/docs/project_notes/archive/trunk-v9.2-complete/.planning_research/orientation.md +0 -51
  99. package/docs/project_notes/archive/trunk-v9.2-complete/audit/plan-rename-hitlist.md +0 -654
  100. package/docs/project_notes/archive/trunk-v9.2-complete/blueprint-conflicts.md +0 -109
  101. package/docs/project_notes/archive/trunk-v9.2-complete/blueprints/database-architect.md +0 -416
  102. package/docs/project_notes/archive/trunk-v9.2-complete/blueprints/devops-infrastructure.md +0 -514
  103. package/docs/project_notes/archive/trunk-v9.2-complete/blueprints/technical-writer.md +0 -788
  104. package/docs/project_notes/archive/trunk-v9.2-complete/build_brief.md +0 -119
  105. package/docs/project_notes/archive/trunk-v9.2-complete/build_report.md +0 -250
  106. package/docs/project_notes/archive/trunk-v9.2-complete/detail_brief.md +0 -94
  107. package/docs/project_notes/archive/trunk-v9.2-complete/plan.md +0 -182
  108. package/docs/project_notes/archive/trunk-v9.2-complete/planning_brief.md +0 -96
  109. package/docs/project_notes/archive/trunk-v9.2-complete/prompt_brief.md +0 -60
  110. package/docs/project_notes/archive/trunk-v9.2-complete/prompt_output.json +0 -98
  111. package/docs/project_notes/archive/trunk-v9.2-complete/scratch/database-architect-decisions.json +0 -72
  112. package/docs/project_notes/archive/trunk-v9.2-complete/scratch/database-architect-research-plan.md +0 -10
  113. package/docs/project_notes/archive/trunk-v9.2-complete/scratch/database-architect-stage1.md +0 -226
  114. package/docs/project_notes/archive/trunk-v9.2-complete/scratch/devops-infrastructure-decisions.json +0 -71
  115. package/docs/project_notes/archive/trunk-v9.2-complete/scratch/devops-infrastructure-research-plan.md +0 -7
  116. package/docs/project_notes/archive/trunk-v9.2-complete/scratch/devops-infrastructure-stage1.md +0 -164
  117. package/docs/project_notes/archive/trunk-v9.2-complete/scratch/technical-writer-decisions.json +0 -88
  118. package/docs/project_notes/archive/trunk-v9.2-complete/scratch/technical-writer-research-plan.md +0 -7
  119. package/docs/project_notes/archive/trunk-v9.2-complete/scratch/technical-writer-stage1.md +0 -266
  120. package/docs/project_notes/archive/trunk-v9.2-complete/team_assignment.json +0 -108
  121. package/docs/project_notes/archive/trunk-v9.2-complete/test_brief.md +0 -75
  122. package/docs/project_notes/archive/trunk-v9.2-complete/test_report.md +0 -26
  123. package/docs/project_notes/archive/trunk-v9.2-complete/verification/devops-infrastructure-verification.md +0 -172
  124. package/docs/project_notes/branches/.gitkeep +0 -0
  125. package/docs/project_notes/bugs.md +0 -41
  126. package/docs/project_notes/decisions.md +0 -147
  127. package/docs/project_notes/issues.md +0 -101
  128. package/docs/project_notes/key_facts.md +0 -88
  129. package/docs/project_notes/trunk/.gitkeep +0 -0
  130. package/docs/project_notes/trunk/discovery_brief.md +0 -40
  131. package/docs/project_notes/v9.2-optimization-plan.md +0 -193
@@ -1,342 +0,0 @@
1
- # Intuition Architecture
2
-
3
- This document describes the technical architecture of the Intuition three-agent system.
4
-
5
- ## System Overview
6
-
7
- Intuition is a skill-based system for Claude Code that implements a three-phase workflow for software development:
8
-
9
- ```
10
- Discovery → Planning → Execution
11
- (Waldo) (Magellan) (Faraday)
12
- ```
13
-
14
- Each phase is handled by a specialized agent with focused responsibilities, connected through file-based handoffs in project memory.
15
-
16
- ## Design Principles
17
-
18
- ### 1. Separation of Concerns
19
- Each agent has a single, focused responsibility:
20
- - Waldo: Discovery and dialogue
21
- - Magellan: Research and planning
22
- - Faraday: Orchestration and execution
23
-
24
- ### 2. Clean Context
25
- By separating phases, each agent starts with clean, focused context:
26
- - Waldo only holds dialogue state
27
- - Magellan reads synthesis from files
28
- - Faraday reads plans from files
29
-
30
- ### 3. File-Based Handoffs
31
- Agents communicate through project memory files, not conversation context:
32
- - `discovery_brief.md` - Waldo → Magellan
33
- - `plan.md` - Magellan → Faraday
34
- - `state.json` - Workflow coordination
35
-
36
- ### 4. Resume Support
37
- All agents can resume interrupted work by reading state from project memory.
38
-
39
- ## Skill Structure
40
-
41
- ```
42
- skills/
43
- ├── intuition-start/
44
- │ └── SKILL.md # Context loader, workflow status
45
- ├── intuition-initialize/
46
- │ ├── SKILL.md # Project memory setup
47
- │ └── references/
48
- │ └── state_template.json
49
- ├── intuition-discovery/
50
- │ ├── SKILL.md # Waldo's interface
51
- │ └── references/
52
- │ ├── waldo_core.md # GAPP methodology
53
- │ └── templates/
54
- │ └── discovery_brief_template.md
55
- ├── intuition-plan/
56
- │ ├── SKILL.md # Magellan's interface
57
- │ └── references/
58
- │ ├── magellan_core.md # Planning methodology
59
- │ └── templates/
60
- │ └── plan_template.md
61
- └── intuition-execute/
62
- ├── SKILL.md # Faraday's interface
63
- └── references/
64
- └── faraday_core.md # Execution methodology
65
- ```
66
-
67
- ## State Management
68
-
69
- ### State File Location
70
- `docs/project_notes/.project-memory-state.json`
71
-
72
- ### State Schema (v2.0)
73
-
74
- ```json
75
- {
76
- "initialized": true,
77
- "version": "2.0",
78
-
79
- "workflow": {
80
- "status": "none|discovery|planning|executing|complete",
81
-
82
- "discovery": {
83
- "completed": false,
84
- "completed_at": null,
85
- "brief_file": "docs/project_notes/discovery_brief.md",
86
- "resume_data": null
87
- },
88
-
89
- "planning": {
90
- "completed": false,
91
- "completed_at": null,
92
- "plan_file": "docs/project_notes/plan.md",
93
- "approved": false,
94
- "approved_at": null,
95
- "resume_data": null
96
- },
97
-
98
- "execution": {
99
- "started": false,
100
- "started_at": null,
101
- "completed": false,
102
- "completed_at": null,
103
- "tasks_completed": 0,
104
- "tasks_total": 0,
105
- "resume_data": null
106
- }
107
- },
108
-
109
- "agents": {
110
- "waldo": { "greeted": false },
111
- "magellan": { "greeted": false },
112
- "faraday": { "greeted": false }
113
- },
114
-
115
- "history": {
116
- "discovery_revisions": 0,
117
- "planning_revisions": 0,
118
- "last_activity": null
119
- }
120
- }
121
- ```
122
-
123
- ### State Transitions
124
-
125
- ```
126
- none → discovery (when /intuition-discovery starts)
127
- discovery → planning (when discovery completes)
128
- planning → executing (when plan is approved)
129
- executing → complete (when execution finishes)
130
- complete → discovery (when new workflow starts)
131
- ```
132
-
133
- ## Data Flow
134
-
135
- ### Discovery Phase (Waldo)
136
-
137
- **Input:**
138
- - User dialogue
139
- - (Optional) Existing project memory
140
-
141
- **Process:**
142
- 1. GAPP dialogue (Problem → Goals → UX Context → Personalization)
143
- 2. Clarifying questions
144
- 3. Synthesize into discovery brief
145
-
146
- **Output:**
147
- - `docs/project_notes/discovery_brief.md`
148
- - Updated `state.json` (workflow.status = "discovery", discovery.completed = true)
149
-
150
- ### Planning Phase (Magellan)
151
-
152
- **Input:**
153
- - `docs/project_notes/discovery_brief.md`
154
- - Codebase (via Research agents)
155
-
156
- **Process:**
157
- 1. Read discovery brief
158
- 2. Assess scope (auto-detect planning depth)
159
- 3. Launch parallel Research agents
160
- 4. Synthesize plan
161
- 5. Present for user approval
162
-
163
- **Output:**
164
- - `docs/project_notes/plan.md`
165
- - Updated `state.json` (workflow.status = "planning", planning.approved = true)
166
-
167
- ### Execution Phase (Faraday)
168
-
169
- **Input:**
170
- - `docs/project_notes/plan.md`
171
- - `docs/project_notes/discovery_brief.md`
172
- - Codebase
173
-
174
- **Process:**
175
- 1. Read plan and discovery context
176
- 2. Confirm with user
177
- 3. Create tasks from plan
178
- 4. Delegate to sub-agents (parallel when possible)
179
- 5. Verify outputs
180
- 6. Update project memory
181
-
182
- **Output:**
183
- - Implemented code changes
184
- - Updated project memory (bugs.md, decisions.md, etc.)
185
- - Updated `state.json` (workflow.status = "complete")
186
-
187
- ## Sub-Agent Architecture
188
-
189
- ### Available Sub-Agents
190
-
191
- | Agent | Used By | Purpose |
192
- |-------|---------|---------|
193
- | Research | Waldo, Magellan | Explore codebase |
194
- | Security Expert | Magellan, Faraday | Security review |
195
- | Code Writer | Faraday | Implementation |
196
- | Test Runner | Faraday | Testing |
197
- | Code Reviewer | Faraday | Quality review |
198
- | Documentation | Faraday | Doc updates |
199
- | Technical Spec Writer | Faraday | Specifications |
200
- | Communications Specialist | Faraday | User-facing docs |
201
-
202
- ### Parallel Execution
203
-
204
- Both Magellan and Faraday can run sub-agents in parallel:
205
-
206
- ```
207
- Magellan (Planning):
208
- ├── Research Agent 1: Authentication patterns
209
- ├── Research Agent 2: Database schema
210
- └── Research Agent 3: API routing
211
- ↓ (all complete)
212
- Synthesize findings
213
-
214
- Faraday (Execution):
215
- ├── Code Writer 1: User model
216
- ├── Code Writer 2: Product model
217
- └── Code Writer 3: Order model
218
- ↓ (all complete)
219
- Verify each independently
220
- ```
221
-
222
- ## File Formats
223
-
224
- ### discovery_brief.md
225
-
226
- ```markdown
227
- # Discovery Brief
228
-
229
- ## Problem
230
- [Core challenge and context]
231
-
232
- ## Goals
233
- [Success criteria]
234
-
235
- ## User Context
236
- [Personas and workflows]
237
-
238
- ## Personalization / Motivation
239
- [What drives this work]
240
-
241
- ## Scope
242
- [In scope / out of scope]
243
-
244
- ## Assumptions
245
- [With confidence levels]
246
- ```
247
-
248
- ### plan.md
249
-
250
- ```markdown
251
- # Plan: [Title]
252
-
253
- ## Objective
254
- [What will be accomplished]
255
-
256
- ## Discovery Summary
257
- [Key insights from Waldo]
258
-
259
- ## Research Context
260
- [Codebase findings]
261
-
262
- ## Approach
263
- [Strategy and rationale]
264
-
265
- ## Tasks
266
- [With acceptance criteria, dependencies]
267
-
268
- ## Risks & Mitigations
269
- [Identified risks]
270
-
271
- ## Execution Notes for Faraday
272
- [Guidance for execution]
273
- ```
274
-
275
- ## Resume Mechanism
276
-
277
- Each agent stores resume data in `state.json`:
278
-
279
- **Waldo:**
280
- - Current GAPP phase
281
- - Key insights captured
282
- - Open questions
283
-
284
- **Magellan:**
285
- - Research completed
286
- - Draft progress
287
- - Current synthesis state
288
-
289
- **Faraday:**
290
- - Tasks completed
291
- - Current task
292
- - Checkpoint reached
293
-
294
- On resume, agents read their resume_data and continue from last checkpoint.
295
-
296
- ## Discovery Revision Flow
297
-
298
- When discovery is revised:
299
-
300
- 1. User runs `/intuition-discovery` again
301
- 2. Waldo updates `discovery_brief.md`
302
- 3. State tracks revision: `history.discovery_revisions++`
303
- 4. Magellan detects timestamp change
304
- 5. Magellan offers to re-plan
305
- 6. If yes, new plan created; old plan archived
306
-
307
- ## Error Handling
308
-
309
- ### Workflow Validation
310
- Each skill validates workflow state before proceeding:
311
- - Magellan requires discovery to be complete
312
- - Faraday requires plan to be approved
313
-
314
- ### Graceful Degradation
315
- If state.json is missing or corrupted:
316
- - Skills fall back to checking for file existence
317
- - User prompted to re-initialize if needed
318
-
319
- ### Sub-Agent Failures
320
- Faraday handles sub-agent failures with:
321
- 1. Retry with additional context
322
- 2. Decompose into smaller tasks
323
- 3. Escalate to user
324
-
325
- ## Security Considerations
326
-
327
- - Security Expert review is MANDATORY before any commit
328
- - No skipping or bypassing security gates
329
- - Faraday verifies security review before completing execution
330
-
331
- ## Extension Points
332
-
333
- ### Adding New Sub-Agents
334
- 1. Document in each skill's sub_agents.md
335
- 2. Add delegation patterns to core reference
336
- 3. Update SKILL.md with agent description
337
-
338
- ### Adding New Workflow Phases
339
- 1. Add state tracking in state_template.json
340
- 2. Create new skill directory
341
- 3. Update intuition-start for status detection
342
- 4. Document handoff files and formats
@@ -1,210 +0,0 @@
1
- # Intuition Workflow Guide
2
-
3
- Welcome to Intuition! This guide explains how to use the three-phase workflow for planning and executing software projects.
4
-
5
- ## Overview
6
-
7
- Intuition uses three specialized agents, each focused on a specific phase of work:
8
-
9
- | Phase | Skill | Agent | Purpose |
10
- |-------|-------|-------|---------|
11
- | 1. Discovery | `/intuition-discovery` | **Waldo** | Explore problems, goals, and motivations through dialogue |
12
- | 2. Planning | `/intuition-plan` | **Magellan** | Synthesize discovery into executable plans |
13
- | 3. Execution | `/intuition-execute` | **Faraday** | Implement plans with methodical precision |
14
-
15
- Each agent has a focused role, which keeps context clean and improves success rate.
16
-
17
- ## Quick Start
18
-
19
- ```bash
20
- # Start your session
21
- /intuition-start
22
-
23
- # Explore your problem with Waldo
24
- /intuition-discovery
25
-
26
- # Create a plan with Magellan
27
- /intuition-plan
28
-
29
- # Execute with Faraday
30
- /intuition-execute
31
- ```
32
-
33
- ## The Three Phases
34
-
35
- ### Phase 1: Discovery with Waldo
36
-
37
- **What happens:** Waldo guides you through the GAPP framework to surface authentic intentions before planning.
38
-
39
- **GAPP Framework:**
40
- - **Problem** - What's the core challenge?
41
- - **Goals** - What does success look like?
42
- - **UX Context** - Who will use this and how?
43
- - **Personalization** - What drives this work for you?
44
-
45
- **What you'll experience:**
46
- - Socratic questioning that helps you think deeper
47
- - Systems thinking perspective on how problems connect
48
- - Clarifying questions to validate understanding
49
-
50
- **Output:** `docs/project_notes/discovery_brief.md`
51
-
52
- **Example:**
53
- ```
54
- You: /intuition-discovery
55
- Waldo: What's the core challenge you're trying to solve?
56
- You: Our API is too slow for large data requests.
57
- Waldo: What happens when this slowness occurs? Who's affected?
58
- ...
59
- ```
60
-
61
- ### Phase 2: Planning with Magellan
62
-
63
- **What happens:** Magellan reads the discovery brief, researches your codebase, and creates a structured plan.
64
-
65
- **What Magellan does:**
66
- - Reads your discovery brief
67
- - Launches Research agents to explore the codebase
68
- - Synthesizes insights into a coherent strategy
69
- - Creates tasks with dependencies and acceptance criteria
70
- - Presents the plan for your approval
71
-
72
- **Output:** `docs/project_notes/plan.md`
73
-
74
- **Example:**
75
- ```
76
- You: /intuition-plan
77
- Magellan: I've read your discovery brief about API performance. Let me research the codebase...
78
-
79
- [Research agents explore in parallel]
80
-
81
- Magellan: Based on discovery and research, here's my recommended plan:
82
- - Task 1: Add caching layer to data endpoints
83
- - Task 2: Implement pagination for large results
84
- - Task 3: Add performance monitoring
85
- ...
86
- ```
87
-
88
- ### Phase 3: Execution with Faraday
89
-
90
- **What happens:** Faraday reads the approved plan and orchestrates implementation through specialized sub-agents.
91
-
92
- **What Faraday does:**
93
- - Reads the plan and discovery brief
94
- - Confirms approach with you
95
- - Delegates tasks to sub-agents (Code Writer, Test Runner, etc.)
96
- - Verifies outputs against acceptance criteria
97
- - Reports completion with files modified
98
-
99
- **Sub-agents available:**
100
- - Code Writer, Test Runner, Documentation
101
- - Research, Code Reviewer, Security Expert
102
- - Technical Spec Writer, Communications Specialist
103
-
104
- **Example:**
105
- ```
106
- You: /intuition-execute
107
- Faraday: I've read the plan. Here's my execution approach:
108
- - Tasks 1-3 can run in parallel (different files)
109
- - Security review is mandatory before completion
110
-
111
- Ready to proceed?
112
-
113
- You: Yes
114
- Faraday: [Delegates to Code Writer agents in parallel]
115
- ...
116
- Faraday: Execution complete. 3 tasks finished, all tests passing.
117
- ```
118
-
119
- ## Workflow Status
120
-
121
- Intuition tracks your progress through the workflow in `docs/project_notes/.project-memory-state.json`.
122
-
123
- Run `/intuition-start` at any time to see where you are:
124
-
125
- ```
126
- /intuition-start
127
-
128
- Workflow Status: Discovery complete, awaiting planning
129
- - Discovery: ✓ Complete
130
- - Planning: Not started
131
- - Execution: Not started
132
-
133
- Suggested Next Step: Run /intuition-plan
134
- ```
135
-
136
- ## File Outputs
137
-
138
- Each phase produces files in your project memory:
139
-
140
- ```
141
- docs/project_notes/
142
- ├── .project-memory-state.json (workflow tracking)
143
- ├── discovery_brief.md (from Waldo)
144
- ├── plan.md (from Magellan)
145
- ├── bugs.md (project memory)
146
- ├── decisions.md (project memory)
147
- ├── key_facts.md (project memory)
148
- └── issues.md (project memory)
149
- ```
150
-
151
- ## Resume Support
152
-
153
- All three skills support resuming interrupted work:
154
-
155
- - **Waldo** resumes from the last GAPP phase
156
- - **Magellan** resumes from research or draft state
157
- - **Faraday** resumes from the last completed task
158
-
159
- Just run the skill again and it will pick up where you left off.
160
-
161
- ## Discovery Revision
162
-
163
- If you need to revise your discovery (maybe you learned something new):
164
-
165
- 1. Run `/intuition-discovery` again
166
- 2. Waldo will update the discovery brief
167
- 3. Magellan will detect the change and offer to re-plan
168
-
169
- This keeps plans aligned with your current understanding.
170
-
171
- ## Best Practices
172
-
173
- 1. **Start with `/intuition-start`** - Load context at the beginning of each session
174
-
175
- 2. **Don't skip discovery** - The GAPP framework significantly improves plan quality
176
-
177
- 3. **Trust the agents** - Each has a focused role; let them do their job
178
-
179
- 4. **Approve before execution** - Always review Magellan's plan before Faraday executes
180
-
181
- 5. **Use project memory** - Initialize with `/intuition-initialize` for persistent context
182
-
183
- ## Troubleshooting
184
-
185
- **"No discovery brief found"**
186
- - Run `/intuition-discovery` first to create one
187
-
188
- **"Plan not approved"**
189
- - Review `docs/project_notes/plan.md` and tell Magellan to proceed
190
-
191
- **"Workflow out of sync"**
192
- - Run `/intuition-start` to see current status and reset if needed
193
-
194
- ## Agent Personalities
195
-
196
- Each agent has a distinct personality:
197
-
198
- - **Waldo** (after Ralph Waldo Emerson) - Thoughtful, curious, philosophical. Asks probing questions.
199
-
200
- - **Magellan** (after Ferdinand Magellan) - Strategic, organized, confident. Turns vision into plans.
201
-
202
- - **Faraday** (after Michael Faraday) - Methodical, precise, rigorous. Transforms plans into reality.
203
-
204
- ## Getting Help
205
-
206
- - `/intuition-start` - See current status and get suggestions
207
- - Check `docs/project_notes/` for all workflow files
208
- - Each skill's SKILL.md has detailed documentation
209
-
210
- Happy building!