Structured & parametrized brainstorming (interview → domain → tree triage)

[rucka]

Epic Information

Epic ID: EP-205
Initiative: Process Engine & Orchestration #200
Theme: Structured discovery
Epic Owner: Foomakers Product Team
Status: Planning
Priority: P0
Epic Points: 18 (estimated)
Target Release: Slice ① (sequencing R4.7)

Epic Statement

As a product team using pair on an existing project
I need a structured, parametrized brainstorming process (free theme or issue-rooted)
So that features are discovered, integrated with the domain model and triaged into the existing epic/story tree without rewriting the PRD

Epic Context

The ONLY new process skill (D24). 3 phases: (1) interview via grill engine — one question at a time with recommendation, explores KB/codebase before asking; (2) domain integration — invokes map-subdomains (broad/functional) or map-contexts (punctual/technical) scoped to what the session touched; (3) triage into epic/story tree integrated with the existing backlog (to-issues pattern, vertical slices) → controlled skill pipeline from a branch.

Business Value & Objectives

Primary Business Goals

1. Goal 1: Feature discovery on existing projects without PRD rewrite (R3.1).
2. Goal 2: Requirements sharpened before structuring (R3.7): questions first, raw blob, then plan-epics → plan-stories.
3. Goal 3: Stories informed by project KB/adoption, not only generic templates (R3.13).

Success Metrics (KPIs)

• Brainstorm output integration - Target: 100% of phase-3 trees linked to existing backlog items
  • Measurement method: created issues reference parent/related items
  • Current baseline: no brainstorming skill exists

Problem Statement & Market Opportunity

Current State

No brainstorming step exists; new features enter via manual epic/story writing; domain knowledge is not consulted; PRD rewrite is the only structured path.

Target State

pair-process-brainstorm covers free-theme and issue-rooted discovery at two levels (broad/punctual), functional or technical orientation deduced from issue type/tags, output integrated under the root.

Solution Overview

Core Solution Approach

Adapt mattpocock grilling + to-issues patterns: relentless interview with recommendations, codebase/KB exploration before questions, vertical-slice triage.

Key Capabilities

1. Parametrized (D24): no args = free theme; $root <issue-id> = brainstorm on the issue — level (broad R3.4 / punctual) and orientation (functional/technical) deduced from type and tags; phase 3 integrates the tree under the root.
2. grill engine — reusable interview capability; sync mode = AI↔human alignment (R3.11), shared with refine-story.
3. Compound on existing (R3.1): understands where to insert (new epic vs story on open epic).
4. Adoption-informed stories (R3.13).

Epic Breakdown

User Stories (High-Level)

Must-Have Stories (P0)

• US: As a developer I want pair-capability-grill (one question at a time + recommendation; sync mode) so that interviews are reusable across skills
• US: As a product team I want pair-process-brainstorm (3 phases, $root param, orientation from issue type) so that discovery is structured
• US: As a planner I want the to-issues triage pattern in plan-epics/plan-stories (vertical slices, integration with existing) so that trees merge into the backlog

Should-Have Stories (P1)

• US: As a planner I want adoption-informed story generation (R3.13) so that stories reflect project history and decisions

Epic Acceptance Criteria

• AC1: Brainstorm on existing project never modifies the PRD
• AC2: Phase-3 output = Draft epic/story tree in PM tool linked to existing items
• AC3: Features conflicting with registered domain rules are flagged citing the DDR
• AC4: Works with no arguments (free theme) and with $root (issue-scoped)

Timeline & Roadmap

Critical Path Dependencies

• Soft: Domain model epic (Domain model: context map, DDR, analysis log #203) — phase 2 degrades gracefully if context-map.md absent

Success Validation

Launch Criteria

• Functionality: All must-have stories completed and tested
• Documentation: Docs site updated for every feature/artifact of this epic
• CLI: apps/pair-cli updated where install/update/distribution is touched

---

Appendix

Related Documentation

• Requirements R3.1–R3.4, R3.7, R3.13 · Spec G3 in pair-requirements-triage.md · Decision D24