eai-cli 0.0.0-bootstrap.0

package/resources/gofer/templates/problem-brief-template.md

@@ -0,0 +1,85 @@
+---
+feature: '{{feature-name}}'
+created: '{{ISO-timestamp}}'
+validated-by: Gofer + {{User}}
+status: draft
+---
+
+# Problem Brief: {{feature-name}}
+
+## Problem Statement
+
+**As Stated**: {{original-problem-description}}
+
+**Refined**: {{clearer-version-after-5-whys}}
+
+## Root Cause Analysis (5 Whys)
+
+| Level | Question         | Answer     |
+| ----- | ---------------- | ---------- |
+| Why 1 | Why {{problem}}? | Because... |
+| Why 2 | Why {{cause-1}}? | Because... |
+| Why 3 | Why {{cause-2}}? | Because... |
+| Why 4 | Why {{cause-3}}? | Because... |
+| Why 5 | Why {{cause-4}}? | ROOT CAUSE |
+
+**Root Cause Summary**: {{one-sentence-root-cause}}
+
+## Stakeholder Impact
+
+| Stakeholder | Impact Level | Frequency | Cost per Occurrence | Annual Impact |
+| ----------- | ------------ | --------- | ------------------- | ------------- |
+| {{role-1}}  | High/Med/Low | {{freq}}  | {{time-or-money}}   | {{estimate}}  |
+| {{role-2}}  | High/Med/Low | {{freq}}  | {{time-or-money}}   | {{estimate}}  |
+
+## Business Case
+
+| Metric                         | Value            |
+| ------------------------------ | ---------------- |
+| Cost of doing nothing (annual) | {{estimate}}     |
+| Estimated value of solving     | {{estimate}}     |
+| Payback period                 | {{weeks-months}} |
+| Confidence level               | High/Med/Low     |
+
+## Success Metrics
+
+| Metric     | Current Baseline | Target   | Measurement Method |
+| ---------- | ---------------- | -------- | ------------------ |
+| {{metric}} | {{current}}      | {{goal}} | {{how-measured}}   |
+
+## Constraints
+
+| Constraint Type | Description  | Impact on Solution         |
+| --------------- | ------------ | -------------------------- |
+| Budget          | {{amount}}   | {{how-it-limits-options}}  |
+| Timeline        | {{deadline}} | {{what-must-be-ready}}     |
+| Technical       | {{limit}}    | {{what-it-prevents}}       |
+| Regulatory      | {{standard}} | {{what-must-be-compliant}} |
+
+## Problem-Solution Fit
+
+**Software needed?** Yes/No/Partial
+
+**Simpler alternatives considered**:
+
+1. **Process change**: {{description}} — {{why-it-does-or-doesnt-work}}
+2. **Existing tool**: {{description}} — {{why-it-does-or-doesnt-work}}
+3. **Manual workaround**: {{description}} — {{why-it-does-or-doesnt-work}}
+
+## Assumptions
+
+- [ ] {{assumption-1}} — UNVALIDATED
+- [ ] {{assumption-2}} — UNVALIDATED
+
+## Recommendation
+
+**Proceed**: YES/NO/CONDITIONAL **Confidence**: High/Med/Low **Rationale**:
+{{2-3-sentences-plain-english}}
+
+## Approval
+
+- [ ] Problem validated by stakeholder
+- [ ] Root cause confirmed
+- [ ] Business case accepted
+- [ ] Constraints acknowledged
+- [ ] Assumptions documented

package/resources/gofer/templates/proposal-review-template.md

@@ -0,0 +1,79 @@
+---
+feature: '[Feature Name]'
+created: '[ISO timestamp]'
+status: pending_review
+recommendedScenario: '[short label]'
+recommendedArchitecture: '[short label]'
+selectedOption: ''
+approvedBy: ''
+approvedAt: ''
+---
+
+<!--
+  This template is filled in by /1_gofer_research.
+  It is the approval gate between research.md and spec.md.
+  Location: .specify/specs/[###-feature-name]/proposal-review.md
+-->
+
+# Proposal Review: [Feature Name]
+
+## What We Found
+
+[Short, evidence-backed summary of the research findings]
+
+## Business Scenarios Considered
+
+| Scenario   | User Value | Delivery Trade-off | Recommendation |
+| ---------- | ---------- | ------------------ | -------------- |
+| [Option 1] | [Value]    | [Trade-off]        | [Adopt/defer]  |
+| [Option 2] | [Value]    | [Trade-off]        | [Adopt/defer]  |
+
+## Recommended Business Scenario
+
+[What should be specified next and why]
+
+## Pipeline Mode Decision
+
+- **Classification**: [application delivery | non-app work]
+- **Shared numbered stages preserved**: yes
+- **App-delivery-only gates**: [preview, approval, service fit | not applicable]
+
+## Technology Architecture Recommendation
+
+### Recommended Architecture
+
+[Plain-language architecture direction]
+
+### Architecture Options
+
+| Option     | Why choose it | Why not choose it now |
+| ---------- | ------------- | --------------------- |
+| [Option 1] | [Benefit]     | [Trade-off]           |
+| [Option 2] | [Benefit]     | [Trade-off]           |
+
+## Key Decisions and Why
+
+- [Decision]: [Rationale]
+- [Decision]: [Rationale]
+- [Preview strategy]: [Why this is the right first MVP or why it is not applicable]
+- [Service-fit approach]: [Why this capability-selection approach is right or not applicable]
+
+## What Can Change Before Specification
+
+- Scope changes the user may request
+- Architecture changes the user may request
+- Options that can be revisited before writing `spec.md`
+
+## Open Questions
+
+- [ ] [Question needing user input]
+- [ ] [Another question]
+
+## User Feedback and Overrides
+
+- Pending user review
+
+## Approval
+
+- Status: pending_review
+- Next action: user approves or requests changes before `/2_gofer_specify`

package/resources/gofer/templates/research-template.md

@@ -0,0 +1,222 @@
+---
+date: '[ISO timestamp]'
+researcher: Gofer
+feature: '[Feature Name]'
+status: complete
+codebase_type: '[greenfield | brownfield]'
+---
+
+<!--
+  This template is filled in by /1_gofer_research (or legacy /1_research_codebase).
+  Recommended: Use /0_gofer_start to auto-chain the entire pipeline.
+  Location: .specify/specs/[###-feature-name]/research.md
+  Pair this with proposal-review.md before /2_gofer_specify runs.
+-->
+
+# Research: [Feature Name]
+
+## Executive Summary
+
+[Three to five plain-language bullets covering what was researched, why it
+matters, the recommended direction, the biggest risk, and the next decision.]
+
+## Feature Summary
+
+[Brief description of what we're building]
+
+## Visual Summary
+
+Use simple source-controlled visuals when they make the research easier to
+understand. Prefer Mermaid for Markdown-native diagrams, Marp for stakeholder
+slides, D2 for compact system/process sketches when Mermaid is too cramped, and
+Structurizr/C4 when the architecture needs model-as-code consistency.
+
+| Visual                          | Audience            | Question answered                               | Source / render proof |
+| ------------------------------- | ------------------- | ----------------------------------------------- | --------------------- |
+| `visuals/c4-context.md`         | CTO / delivery      | Who uses the system and what does it depend on? | [path]                |
+| `visuals/capability-heatmap.md` | Business / delivery | Which capabilities matter most?                 | [path]                |
+| `presentation.marp.md`          | Stakeholders        | What is the short story for review?             | [path or N/A]         |
+
+If branded stakeholder output is in scope, record discovered brand sources
+(`.specify/memory/brand-profile.json`, brand guide, logo paths, consulting-firm
+style requirements) and whether `/8_gofer_branding` should run before
+stakeholder communications are generated.
+
+## Application Classification
+
+- **Mode**: [application delivery | non-app work]
+- **Shared numbered stages preserved**: [yes]
+- **Why this classification applies**: [rationale]
+
+## Business Scenario Analysis
+
+### Scenario Options Considered
+
+| Scenario   | User/Business Fit | Delivery Trade-off | Recommendation |
+| ---------- | ----------------- | ------------------ | -------------- |
+| [Option 1] | [Why it fits]     | [Cost/complexity]  | [Adopt/defer]  |
+| [Option 2] | [Why it fits]     | [Cost/complexity]  | [Adopt/defer]  |
+
+### Recommended Scenario
+
+[Which scenario should move forward into specification and why]
+
+## Codebase Analysis
+
+### Where to Implement
+
+| Component     | Location          | Purpose        |
+| ------------- | ----------------- | -------------- |
+| [Component 1] | `path/to/file.ts` | [What it does] |
+| [Component 2] | `path/to/dir/`    | [What it does] |
+
+### Existing Patterns to Follow
+
+#### Pattern 1: [Name]
+
+Found in: `path/to/example.ts:45-67`
+
+```typescript
+// Example code showing the pattern
+```
+
+Why relevant: [Explanation]
+
+#### Pattern 2: [Name]
+
+...
+
+### Integration Points
+
+1. **[Integration 1]**: How to connect with existing code
+2. **[Integration 2]**: ...
+
+### Related Code
+
+- `path/file.ts:123` - [Description]
+- `path/other.ts:45` - [Description]
+
+## Technology Decisions
+
+### Decision 1: [Topic]
+
+- **Choice**: [What we'll use]
+- **Rationale**: [Why]
+- **Alternatives considered**: [What else]
+
+### Decision 2: [Topic]
+
+...
+
+## UI-First App Delivery Research _(application delivery only)_
+
+### Preview Strategy
+
+- **Smallest useful MVP to show first**: [description]
+- **Profile choice**: [external / internal / hybrid]
+- **Package lane**: [public-package / internal-app / hybrid-adapter / app-local]
+- **Coupling status**: [source-platform-coupled / source-platform-decoupled /
+  hybrid-adapter]
+- **Public-readiness target**: [required / deferred / not applicable]
+- **EAI App Template constraints**: [approved blocks/patterns to reuse first]
+- **Block catalog discovery**: [`eai --describe`, `eai blocks list`, candidate
+  `eai blocks describe <id>` results, and `eai resources schema` evidence]
+- **Selected block IDs**: [stable IDs, required resources, bindings, override
+  points, Storybook story IDs, theme override points, package lane, coupling
+  status, and custom-block exceptions]
+- **Block porting plan**: [reuse as-is, port to package, or custom-block
+  exception with owner and approval path]
+- **source-platform decoupling plan**: [adapter/resource-schema boundary or
+  approved restricted-source exception]
+- **Branding inputs**: [logos, colors, voice, or "not in scope"]
+- **Preview validation expectation**: [screenshot, local render proof,
+  Playwright-style checks]
+
+### Service-Fit Discovery Inputs
+
+- **Capability discovery sources**: [`eai --describe`, `eai whoami`, `eai tenant
+  select`, `eai resources schema`, `eai verify calls --format json`, or
+  equivalent]
+- **What must be decided after UI approval**: [service selection questions]
+- **Non-app note**: [write "Not applicable" when this feature is non-app work]
+
+## Recommended Architecture Direction
+
+### Recommended Architecture
+
+[Plain-language summary of the architecture direction this feature should use]
+
+### Architecture Options Considered
+
+| Option     | Why choose it | Why not choose it now |
+| ---------- | ------------- | --------------------- |
+| [Option 1] | [Benefit]     | [Trade-off]           |
+| [Option 2] | [Benefit]     | [Trade-off]           |
+
+## Constraints & Considerations
+
+- [Constraint 1]: [Impact on implementation]
+- [Constraint 2]: ...
+
+---
+
+## Brownfield Analysis
+
+_(Include this section for existing codebases)_
+
+### Constraints & Limitations
+
+| Constraint Type   | Description                               | Impact on Implementation   |
+| ----------------- | ----------------------------------------- | -------------------------- |
+| Framework         | [e.g., React 17 - no concurrent features] | [How this limits approach] |
+| Database          | [e.g., PostgreSQL 12, existing schema]    | [Schema constraints]       |
+| API Compatibility | [e.g., Must maintain v1 endpoints]        | [Backward compat needs]    |
+| Performance       | [e.g., Response time < 200ms]             | [Optimization needs]       |
+
+### Technical Debt to Avoid
+
+The following patterns are deprecated or problematic - do NOT use:
+
+| Pattern       | Found In          | Why Avoid | Use Instead          |
+| ------------- | ----------------- | --------- | -------------------- |
+| [Old pattern] | `path/to/file.ts` | [Reason]  | [Preferred approach] |
+
+### Areas Requiring Extra Caution
+
+- **[Area 1]**: [Why it's fragile and what to watch for]
+- **[Area 2]**: [Known issues or gotchas]
+
+### Integration Requirements
+
+| Existing Service | Integration Method | Notes                |
+| ---------------- | ------------------ | -------------------- |
+| [Service 1]      | [API/Import/Event] | [Auth, format, etc.] |
+
+### Downstream Dependencies
+
+Code that depends on areas we're modifying:
+
+- `path/to/dependent.ts:45` - [What it depends on]
+- `path/to/consumer.ts:123` - [What it expects]
+
+### Brownfield Checklist
+
+Before modifying existing code:
+
+- [ ] Understand current behavior (read and trace code flow)
+- [ ] Document what must NOT change (protected boundaries)
+- [ ] Identify downstream dependencies
+- [ ] Add characterization tests if modifying complex logic
+- [ ] Plan rollback strategy for risky changes
+
+---
+
+## Open Questions
+
+- [ ] [Question needing user input]
+- [ ] [Another question]
+
+## Recommendations
+
+1. [Key recommendation for implementation]
+2. [Another recommendation]

package/resources/gofer/templates/reuse-scan-template.md

@@ -0,0 +1,43 @@
+---
+feature: '{{feature-name}}'
+created: '{{ISO-timestamp}}'
+workflowProfile: enterpriseai
+---
+
+# Reuse-Before-Create Scan: {{feature-name}}
+
+## Scan Scope
+
+| Asset Type                     | Search Performed                  | Result     |
+| ------------------------------ | --------------------------------- | ---------- |
+| Existing specs                 | {{paths-or-query}}                | {{result}} |
+| Object types                   | {{paths-or-query}}                | {{result}} |
+| APIs/events                    | {{paths-or-query}}                | {{result}} |
+| Workflows/journeys             | {{paths-or-query}}                | {{result}} |
+| Modules/components             | {{paths-or-query}}                | {{result}} |
+| UI blocks/packages             | {{eai-blocks-or-storybook-query}} | {{result}} |
+| Theme override points          | {{tokens-slots-css-vars-query}}   | {{result}} |
+| source-platform coupling paths | {{imports-or-runtime-query}}      | {{result}} |
+| EnterpriseAI references        | {{paths-or-query}}                | {{result}} |
+
+## Decisions
+
+| Candidate     | Evidence              | Decision                    | Rationale | Owner     |
+| ------------- | --------------------- | --------------------------- | --------- | --------- |
+| {{candidate}} | {{path-or-reference}} | Reuse / Extend / Create New | {{why}}   | {{owner}} |
+
+## Block Porting And Package Profile Decisions
+
+| Candidate Block | Package Lane | Storybook Story ID | Coupling Status     | Decision                        | Public-Readiness Impact |
+| --------------- | ------------ | ------------------ | ------------------- | ------------------------------- | ----------------------- |
+| {{block-id}}    | {{lane}}     | {{story-id-or-na}} | {{coupling-status}} | Reuse / Port / Custom Exception | {{impact-or-na}}        |
+
+## Create-New Exceptions
+
+Every create-new decision must include:
+
+- Why reuse and extension are insufficient.
+- Architecture owner approval.
+- Data/security owner approval when object types, APIs/events, tenant
+  boundaries, or sensitive data are affected.
+- Acceptance tests proving the new contract is required and working.

package/resources/gofer/templates/sequence-diagrams/option-spectrum.yaml

@@ -0,0 +1,178 @@
+# Sequence Diagram Option Spectrum Templates
+#
+# Defines the 5 implementation options spanning efficiency to innovation.
+# Each option has predefined characteristics for consistent generation.
+#
+# @see spec.md FR-021 through FR-025
+
+options:
+  1_minimal:
+    number: 1
+    name: Minimal
+    description: >
+      Bare minimum implementation. Maximum efficiency, minimal complexity.
+      Uses existing patterns and infrastructure with no new dependencies.
+    efficiency_score: 95
+    innovation_score: 10
+    complexity_target: low
+    estimated_effort: "1-2 days"
+    characteristics:
+      - Direct implementation with existing tools
+      - No new dependencies
+      - Minimal error handling (happy path only)
+      - Basic logging only
+      - No AI/ML components
+    risk_profile:
+      - May need significant expansion later
+      - Limited scalability
+      - Minimal user experience polish
+    gen_ai_touchpoints: []  # None for minimal
+
+  2_efficient:
+    number: 2
+    name: Efficient
+    description: >
+      Pragmatic implementation balancing speed and quality.
+      Follows established patterns with reasonable error handling.
+    efficiency_score: 80
+    innovation_score: 30
+    complexity_target: low-medium
+    estimated_effort: "3-5 days"
+    characteristics:
+      - Established patterns and best practices
+      - Standard error handling
+      - Basic validation
+      - One or two strategic improvements
+      - Consider caching where obvious
+    risk_profile:
+      - Moderate technical debt if requirements grow
+      - May miss opportunities for user delight
+    gen_ai_touchpoints:
+      - Optional: AI-assisted input validation
+
+  3_standard:
+    number: 3
+    name: Standard
+    description: >
+      Balanced approach with good architecture foundations.
+      Comprehensive implementation ready for production.
+    efficiency_score: 60
+    innovation_score: 50
+    complexity_target: medium
+    estimated_effort: "1-2 weeks"
+    characteristics:
+      - Full test coverage
+      - Comprehensive error handling
+      - Proper logging and monitoring
+      - Documentation
+      - Extension points for future features
+    risk_profile:
+      - Balanced trade-offs
+      - May be overbuilt for simple use cases
+    gen_ai_touchpoints:
+      - AI-powered suggestions
+      - Smart defaults based on user history
+
+  4_enhanced:
+    number: 4
+    name: Enhanced
+    description: >
+      Feature-rich implementation with modern capabilities.
+      Includes proactive features that anticipate user needs.
+    efficiency_score: 40
+    innovation_score: 70
+    complexity_target: medium-high
+    estimated_effort: "2-3 weeks"
+    characteristics:
+      - Advanced UX patterns
+      - Real-time features
+      - Personalization capabilities
+      - Analytics integration
+      - A/B testing ready
+    risk_profile:
+      - Higher development cost
+      - More maintenance burden
+      - Potential over-engineering
+    gen_ai_touchpoints:
+      - AI-powered recommendations
+      - Predictive user assistance
+      - Natural language processing
+
+  5_innovative:
+    number: 5
+    name: Innovative
+    description: >
+      Cutting-edge implementation pushing boundaries.
+      Maximum innovation with breakthrough user experience.
+    efficiency_score: 20
+    innovation_score: 95
+    complexity_target: high
+    estimated_effort: "1-2 months"
+    characteristics:
+      - Novel interaction patterns
+      - Heavy AI/ML integration
+      - Autonomous features
+      - Adaptive interfaces
+      - Research-level capabilities
+    risk_profile:
+      - Significant investment required
+      - Technology risk (bleeding edge)
+      - May require specialist skills
+      - User adoption uncertainty
+    gen_ai_touchpoints:
+      - AI-driven autonomous agents
+      - Multi-modal AI (text, voice, vision)
+      - Generative AI for content
+      - AI copilot experience
+      - Continuous learning from user behavior
+
+# Scoring guidance
+scoring_formulas:
+  efficiency:
+    description: "How quickly can this be implemented and maintained?"
+    factors:
+      - Development time
+      - Maintenance burden
+      - Resource usage
+      - Team skill match
+
+  complexity:
+    description: "How complex is the implementation?"
+    levels:
+      low: "Few components, simple data flow"
+      medium: "Multiple components, some async operations"
+      high: "Many components, complex state management, distributed concerns"
+
+  innovation:
+    description: "How novel and differentiated is the approach?"
+    factors:
+      - New patterns introduced
+      - User experience differentiation
+      - AI/ML sophistication
+      - Industry-leading features
+
+# Template for Mermaid diagram generation
+mermaid_template: |
+  sequenceDiagram
+      autonumber
+      {{#each actors}}
+      participant {{id}} as {{name}}
+      {{/each}}
+
+      Note over {{first_actor}}: {{option_name}} Option
+
+      {{#each interactions}}
+      {{from}}->>{{to}}: {{action}}
+      {{#if response}}
+      {{to}}-->>{{from}}: {{response}}
+      {{/if}}
+      {{/each}}
+
+      {{#if gen_ai_touchpoints}}
+      Note over AI: Gen AI Integration Points
+      {{#each gen_ai_touchpoints}}
+      rect rgb(200, 220, 255)
+          Note over AI: {{this}}
+      end
+      {{/each}}
+      {{/if}}

package/resources/gofer/templates/service-fit-matrix-template.md

@@ -0,0 +1,29 @@
+---
+feature: '{{feature-name}}'
+created: '{{ISO-timestamp}}'
+workflowProfile: enterpriseai
+status: draft
+---
+
+# Service Fit Matrix: {{feature-name}}
+
+## Package And Coupling Fit
+
+| Field                   | Decision                                                             | Evidence   |
+| ----------------------- | -------------------------------------------------------------------- | ---------- |
+| Profile choice          | External / Internal / Hybrid                                         | {{source}} |
+| Package lane            | {{public-package-internal-app-hybrid-adapter-app-local}}             | {{source}} |
+| Coupling status         | {{source-platform-coupled-source-platform-decoupled-hybrid-adapter}} | {{source}} |
+| Public-readiness target | {{required-deferred-not-applicable}}                                 | {{source}} |
+
+## App Stack Policy
+
+| Stack Layer        | Decision                                                          | Evidence   |
+| ------------------ | ----------------------------------------------------------------- | ---------- |
+| Primary substrate  | EAI Platform, including EAI app template                          | {{source}} |
+| Cloud/support      | Azure or EAI-compatible Azure service                             | {{source}} |
+| Non-EAI technology | Not used / integration / migration reference / approved exception | {{source}} |
+
+| Capability  | User Need | Evidence Source    | Status                                 | Selected Direction | Notes     |
+| ----------- | --------- | ------------------ | -------------------------------------- | ------------------ | --------- |
+| {{service}} | {{need}}  | {{command-or-doc}} | Accessible / Purchasable / Unavailable | {{decision}}       | {{notes}} |