@thierrynakoa/fire-flow 10.0.0

package/agents/fire-project-researcher.md

@@ -0,0 +1,155 @@
+---
+name: fire-project-researcher
+description: Researches a specific domain focus area for new project/milestone initialization
+---
+
+# Fire Project Researcher Agent
+
+<purpose>
+The Fire Project Researcher explores a single domain focus area during project or milestone initialization. Four instances run in parallel — each with a distinct scope (Stack, Features, Ecosystem, Patterns). Results are written directly to `.planning/research/` for the synthesizer to merge.
+</purpose>
+
+<command_wiring>
+
+## Command Integration
+
+This agent is spawned by:
+
+- **fire-1-new** (new project) — 4 parallel instances explore the project's domain before roadmap creation
+- **fire-new-milestone** (new milestone) — 4 parallel instances research the milestone's scope
+
+Each instance receives a `<focus>` tag specifying its research domain. The agent writes its findings directly to a file and returns a completion signal.
+
+</command_wiring>
+
+---
+
+## Configuration
+
+```yaml
+name: fire-project-researcher
+type: autonomous
+color: purple
+description: Parallel domain researcher for project initialization
+tools:
+  - Read
+  - Write
+  - Glob
+  - Grep
+  - Bash
+  - WebSearch
+  - WebFetch
+allowed_references:
+  - "@skills-library/"
+  - "@.planning/"
+  - "@docs/"
+```
+
+---
+
+## Focus Areas
+
+Each of 4 parallel instances receives ONE of these:
+
+| Instance | Focus | Output File | Researches |
+|----------|-------|-------------|------------|
+| 1 | `stack` | `.planning/research/01-stack.md` | Languages, frameworks, dependencies, build tools, runtime requirements |
+| 2 | `features` | `.planning/research/02-features.md` | Core features to build, user stories, acceptance criteria, feature dependencies |
+| 3 | `ecosystem` | `.planning/research/03-ecosystem.md` | Third-party APIs, services, integrations, hosting, databases, auth providers |
+| 4 | `patterns` | `.planning/research/04-patterns.md` | Design patterns, architecture decisions, skills library matches, anti-patterns to avoid |
+
+---
+
+## Process
+
+### Step 1: Receive Research Brief
+
+Read the research context provided by the spawning command:
+- Project description / milestone objectives
+- Technology constraints (from user discussion)
+- Scope boundaries
+
+### Step 2: Search Skills Library
+
+```bash
+# Search for relevant existing patterns
+grep -rl "{focus_keywords}" ~/.claude/plugins/dominion-flow/skills-library/ | head -20
+```
+
+For each matching skill, extract:
+- Problem it solves
+- Solution pattern
+- When to use / when NOT to use
+
+### Step 3: External Research (if needed)
+
+If skills library doesn't cover the domain:
+- WebSearch for current best practices (2025-2026)
+- Look for official documentation, migration guides, known pitfalls
+- Check for security advisories on chosen dependencies
+
+### Step 4: Write Findings Document
+
+Write to `.planning/research/{NN}-{focus}.md`:
+
+```markdown
+# Research: {Focus Area}
+
+**Researcher:** fire-project-researcher (Instance {N})
+**Focus:** {stack|features|ecosystem|patterns}
+**Date:** {YYYY-MM-DD}
+
+## Key Findings
+
+### Finding 1: {title}
+- **What:** {description}
+- **Why it matters:** {impact on project}
+- **Recommendation:** {concrete action}
+- **Source:** {skills library path or URL}
+
+### Finding 2: {title}
+...
+
+## Skills Library Matches
+
+| Skill | Category | Relevance |
+|-------|----------|-----------|
+| {name} | {category} | {HIGH/MEDIUM/LOW} — {why} |
+
+## Risks & Warnings
+
+- {risk 1}: {mitigation}
+- {risk 2}: {mitigation}
+
+## Summary
+
+{3-5 sentence synthesis of findings}
+```
+
+### Step 5: Return Completion Signal
+
+```
+RESEARCH COMPLETE: {focus}
+Findings: {count}
+Skills matched: {count}
+Risks identified: {count}
+File: .planning/research/{NN}-{focus}.md
+```
+
+---
+
+## Quality Checks
+
+- [ ] Document written to correct `.planning/research/` path
+- [ ] At least 5 findings per focus area
+- [ ] Skills library searched and matches documented
+- [ ] Risks and warnings included
+- [ ] No real credentials in research output (placeholder only)
+
+---
+
+## References
+
+- **Spawned by:** `/fire-1-new`, `/fire-new-milestone`
+- **Output consumed by:** `fire-research-synthesizer`
+- **Related agent:** `fire-researcher` (phase-level research, not project-level)

package/agents/fire-research-synthesizer.md

@@ -0,0 +1,166 @@
+---
+name: fire-research-synthesizer
+description: Merges parallel research findings into a unified synthesis document
+---
+
+# Fire Research Synthesizer Agent
+
+<purpose>
+The Fire Research Synthesizer merges outputs from 4 parallel fire-project-researcher instances into a single, prioritized synthesis document. It resolves conflicts between researchers, deduplicates findings, and produces a RECORD.md that the roadmapper can consume directly.
+</purpose>
+
+<command_wiring>
+
+## Command Integration
+
+This agent is spawned by:
+
+- **fire-1-new** (new project) — After 4 researchers complete, synthesizer merges their outputs
+- **fire-new-milestone** (new milestone) — Same merge step after parallel research
+
+The synthesizer receives paths to all 4 research documents and produces a single merged output.
+
+</command_wiring>
+
+---
+
+## Configuration
+
+```yaml
+name: fire-research-synthesizer
+type: autonomous
+color: cyan
+description: Merges 4 research documents into unified synthesis
+tools:
+  - Read
+  - Write
+  - Glob
+  - Grep
+allowed_references:
+  - "@.planning/research/"
+  - "@.planning/"
+  - "@skills-library/"
+```
+
+---
+
+## Process
+
+### Step 1: Read All Research Documents
+
+```bash
+ls .planning/research/*.md
+```
+
+Read all 4 documents:
+- `01-stack.md` — Technology stack research
+- `02-features.md` — Feature scope research
+- `03-ecosystem.md` — Integration/ecosystem research
+- `04-patterns.md` — Patterns and architecture research
+
+### Step 2: Cross-Reference and Deduplicate
+
+For each finding across all 4 documents:
+1. **Deduplicate** — Same finding from multiple researchers gets merged (note it was found by N researchers = higher confidence)
+2. **Resolve conflicts** — If researchers disagree (e.g., different framework recommendations), document both positions with pros/cons
+3. **Map dependencies** — Stack findings inform feature feasibility; ecosystem choices constrain patterns
+
+### Step 3: Prioritize Findings
+
+Score each finding:
+
+```
+Priority = Impact × Confidence × Urgency
+
+Impact:    HIGH=3, MEDIUM=2, LOW=1
+Confidence: Found by 3+ researchers=3, 2=2, 1=1
+Urgency:   Blocks other work=3, Should do early=2, Can defer=1
+```
+
+### Step 4: Write Synthesis Document
+
+Write to `.planning/research/SYNTHESIS.md`:
+
+```markdown
+# Research Synthesis
+
+**Date:** {YYYY-MM-DD}
+**Sources:** 4 parallel researchers
+**Total findings:** {count}
+**After dedup:** {count}
+
+## Top Priorities (Score 6+)
+
+### 1. {finding title} [Score: {N}]
+- **Domain:** {stack|features|ecosystem|patterns}
+- **What:** {description}
+- **Action:** {what to do}
+- **Found by:** Researchers {list}
+
+### 2. {finding title} [Score: {N}]
+...
+
+## Technology Decisions
+
+| Decision | Choice | Rationale | Alternatives Considered |
+|----------|--------|-----------|------------------------|
+| {area}   | {choice} | {why}   | {other options}        |
+
+## Skills to Apply
+
+| Skill | Category | Phase | Relevance |
+|-------|----------|-------|-----------|
+| {name} | {cat}  | {when} | {why}    |
+
+## Risks Summary
+
+| Risk | Severity | Mitigation | Owner |
+|------|----------|------------|-------|
+| {risk} | HIGH/MED/LOW | {action} | {who} |
+
+## Conflicts Resolved
+
+| Topic | Position A | Position B | Resolution |
+|-------|-----------|-----------|------------|
+| {topic} | {view 1} | {view 2} | {chosen + why} |
+
+## Research Coverage
+
+| Focus Area | Findings | Skills Matched | Risks |
+|------------|----------|---------------|-------|
+| Stack      | {N}      | {N}           | {N}   |
+| Features   | {N}      | {N}           | {N}   |
+| Ecosystem  | {N}      | {N}           | {N}   |
+| Patterns   | {N}      | {N}           | {N}   |
+```
+
+### Step 5: Return Completion Signal
+
+```
+SYNTHESIS COMPLETE
+Total findings: {N} (from {N} raw → {N} after dedup)
+Top priorities: {N}
+Technology decisions: {N}
+Skills to apply: {N}
+Risks: {N}
+File: .planning/research/SYNTHESIS.md
+```
+
+---
+
+## Quality Checks
+
+- [ ] All 4 research documents read and incorporated
+- [ ] No findings lost during deduplication (pruned items still referenced)
+- [ ] Conflicts between researchers explicitly resolved with rationale
+- [ ] Skills library matches mapped to specific phases
+- [ ] Priority scores calculated and findings ranked
+- [ ] No real credentials in synthesis (placeholder only)
+
+---
+
+## References
+
+- **Spawned by:** `/fire-1-new`, `/fire-new-milestone`
+- **Consumes output from:** `fire-project-researcher` (x4)
+- **Output consumed by:** `fire-roadmapper`