@iservu-inc/adf-cli 0.10.0 → 0.12.0

package/lib/learning/learning-manager.js

@@ -4,6 +4,7 @@ const storage = require('./storage');
 const { analyzeSkipPatterns } = require('./skip-tracker');
 const { detectPatterns, getPatternSummary } = require('./pattern-detector');
 const { getActiveRules, toggleRule, removeRule } = require('./rule-generator');
+const { showAnalyticsDashboard } = require('./analytics-view');
 
 /**
  * Learning Manager - CLI interface for managing learning data
@@ -70,9 +71,10 @@ class LearningManager {
     console.log(chalk.cyan(`│     1. View Skip History`));
     console.log(chalk.cyan(`│     2. Review Detected Patterns`));
     console.log(chalk.cyan(`│     3. Manage Learned Rules`));
-    console.log(chalk.cyan(`│     4. Learning Settings ${config.enabled ? chalk.green('(✓ Enabled)') : chalk.yellow('(○ Disabled)')}`));
-    console.log(chalk.cyan(`│     5. Clear Learning Data`));
-    console.log(chalk.cyan(`│     6. Back to Main Menu`));
+    console.log(chalk.cyan(`│     4. ${chalk.green('📊 Analytics Dashboard')} ${chalk.gray('(NEW)')}`));
+    console.log(chalk.cyan(`│     5. Learning Settings ${config.enabled ? chalk.green('(✓ Enabled)') : chalk.yellow('(○ Disabled)')}`));
+    console.log(chalk.cyan(`│     6. Clear Learning Data`));
+    console.log(chalk.cyan(`│     7. Back to Main Menu`));
     console.log(chalk.cyan('│'));
     console.log(chalk.cyan.bold('└─────────────────────────────────────────────────────┘\n'));
 
@@ -85,9 +87,10 @@ class LearningManager {
           { name: '1. View Skip History', value: 'history' },
           { name: '2. Review Detected Patterns', value: 'patterns' },
           { name: '3. Manage Learned Rules', value: 'rules' },
-          { name: '4. Learning Settings', value: 'settings' },
-          { name: '5. Clear Learning Data', value: 'clear' },
-          { name: '6. Back to Main Menu', value: 'back' }
+          { name: chalk.green('4. 📊 Analytics Dashboard') + chalk.gray(' (NEW)'), value: 'analytics' },
+          { name: '5. Learning Settings', value: 'settings' },
+          { name: '6. Clear Learning Data', value: 'clear' },
+          { name: '7. Back to Main Menu', value: 'back' }
         ]
       }
     ]);
@@ -102,6 +105,9 @@ class LearningManager {
       case 'rules':
         await this.manageRules();
         break;
+      case 'analytics':
+        await this.showAnalytics();
+        break;
       case 'settings':
         await this.manageSettings();
         break;
@@ -398,6 +404,13 @@ class LearningManager {
     await this.pressEnterToContinue();
   }
 
+  /**
+   * Show analytics dashboard
+   */
+  async showAnalytics() {
+    await showAnalyticsDashboard(this.projectPath);
+  }
+
   /**
    * Clear all learning data
    */

package/lib/templates/shared/agents/architect.md

@@ -9,9 +9,12 @@ dependencies:
   templates:
     - architecture-template.md
     - tech-stack-template.md
+    - openspec-proposal.md
+    - openspec-delta.md
   tasks:
     - design-architecture.md
     - validate-tech-stack.md
+    - create-openspec-proposal.md
   data:
     - constitution.md
     - technical-preferences.md
@@ -222,32 +225,29 @@ Document all key decisions:
 
 ### Phase 6: Validation
 
-```
-1. Technical Feasibility
-   - Can we build this?
-   - Do we have the expertise?
-   - Are there unknown unknowns?
+...
+
+## OpenSpec Brownfield Workflow
 
-2. Performance Validation
-   - Will it meet NFR performance targets?
-   - Scalability headroom adequate?
-   - Bottlenecks identified?
+Use this workflow when modifying existing systems (1 -> n) to maintain a source of truth.
+
+```
+1. Initialize OpenSpec (if first time)
+   npx openspec init
 
-3. Security Validation
-   - OWASP Top 10 addressed?
-   - Data protection adequate?
-   - Compliance requirements met?
+2. Create Change Proposal
+   - Create directory: openspec/changes/<feature-name>/
+   - Create proposal.md using openspec-proposal.md template
+   - Create tasks.md using openspec-tasks.md template
 
-4. Cost Validation
-   - Infrastructure costs projected
-   - Third-party service costs
-   - Development effort estimated
+3. Create Spec Deltas
+   - Identify existing specs in openspec/specs/
+   - Create delta files in openspec/changes/<feature-name>/specs/
+   - Use ## ADDED / ## MODIFIED / ## REMOVED markers
 
-5. Constitutional Compliance
-   - Article 1: Spec-first ✓
-   - Article 3: Simplicity first ✓
-   - Article 8: Security by design ✓
-   - Article 9: Performance as requirement ✓
+4. Review & Align
+   - Present proposal and deltas to the team/user
+   - Iterate based on feedback until agreed
 ```
 
 ## Architecture Patterns
@@ -553,5 +553,5 @@ Ready for SM to create stories.
 ---
 
 **Agent Version**: 1.0.0
-**Framework**: AgentDevFramework-Claude
-**Methodology**: BMAD-METHOD + Software Architecture Best Practices
+**Framework**: AgentDevFramework
+**Methodology**: BMAD-METHOD + Software Architecture Best Practices

package/lib/templates/shared/agents/dev.md

@@ -9,9 +9,11 @@ dependencies:
   templates:
     - story-template.md
     - code-review-template.md
+    - openspec-tasks.md
   tasks:
     - implement-story.md
     - run-tests.md
+    - implement-openspec-change.md
   data:
     - constitution.md
     - technical-preferences.md
@@ -221,24 +223,27 @@ You are a Senior Full-Stack Developer focused on implementing features from deta
 
 ### Phase 4: Handoff
 
+...
+
+## OpenSpec Implementation Workflow
+
+Use this when working on an OpenSpec change proposal.
+
 ```
-1. Mark story as "Ready for QA"
-   - Update story status
-   - Add completion notes
-
-2. Document any deviations from spec
-   - Why deviation was necessary
-   - Impact analysis
-   - Approval obtained
-
-3. Provide test evidence
-   - Test coverage report
-   - All tests passing
-   - Performance benchmarks (if applicable)
-
-4. Update progress tracking
-   - Update sprint board
-   - Notify team
+1. Load Change Context
+   - Read openspec/changes/<change>/proposal.md
+   - Review tasks.md for implementation steps
+   - Study spec deltas in openspec/changes/<change>/specs/
+
+2. Execute Tasks
+   - Follow the TDD process for each task
+   - Mark tasks as complete [x] in openspec/changes/<change>/tasks.md
+   - Save implementation decisions to mem0
+
+3. Finalize & Archive
+   - Ensure all deltas are satisfied
+   - Run: npx openspec archive <change>
+   - Verify specs in openspec/specs/ are updated
 ```
 
 ## Code Quality Standards
@@ -618,7 +623,7 @@ Before marking story complete:
 
 ## Remember
 
-You work from detailed story files with complete context. Your job is **disciplined execution**, not interpretation. When ambiguity exists, ask for clarification rather than assuming intent.
+You work from detailed story files with complete context. Your job is **disciplined execution**, not interpretation. When ambiguity exists, ask for clarification rather than assuming intent.  
 
 **Success Metrics**:
 - Tests pass on first QA review
@@ -630,5 +635,5 @@ You work from detailed story files with complete context. Your job is **discipli
 ---
 
 **Agent Version**: 1.0.0
-**Framework**: AgentDevFramework-Claude
-**Last Updated**: 2025-01-XX
+**Framework**: AgentDevFramework
+**Last Updated**: 2025-01-XX

package/lib/templates/shared/agents/pm.md

@@ -10,10 +10,12 @@ dependencies:
     - prd-template.md
     - epic-template.md
     - user-story-template.md
+    - openspec-proposal.md
   tasks:
     - create-prd.md
     - define-epics.md
     - write-stories.md
+    - create-proposal.md
   data:
     - constitution.md
     - technical-preferences.md
@@ -48,7 +50,7 @@ You are a Product Manager focused on creating comprehensive Product Requirements
 
 ## Primary Responsibilities
 
-### 1. PRD Creation
+### 1. PRD Creation (Path A: Greenfield)
 
 **Create comprehensive Product Requirements Document**:
 - Executive Summary
@@ -62,7 +64,15 @@ You are a Product Manager focused on creating comprehensive Product Requirements
 - Success Metrics
 - Out of Scope
 
-### 2. Requirements Definition
+### 2. Change Proposal (Path B: OpenSpec)
+
+**Create Change Proposal in `openspec/changes/<name>/proposal.md`**:
+- **Why**: The problem or opportunity.
+- **What**: The specific changes required.
+- **Success**: How we know it worked.
+- **Impact**: User impact analysis.
+
+### 3. Requirements Definition
 
 **Define clear, testable requirements**:
 - Functional Requirements (what the system does)
@@ -661,5 +671,5 @@ PRD complete. Ready for architect review.
 ---
 
 **Agent Version**: 1.0.0
-**Framework**: AgentDevFramework-Claude
-**Methodology**: BMAD-METHOD + Agile Best Practices
+**Framework**: AgentDevFramework
+**Methodology**: BMAD-METHOD + Agile Best Practices

package/lib/templates/shared/agents/sm.md

@@ -9,10 +9,12 @@ dependencies:
   templates:
     - story-template.md
     - epic-shard-template.md
+    - openspec-tasks.md
   tasks:
     - draft-story.md
     - validate-story.md
     - coordinate-handoff.md
+    - create-openspec-tasks.md
   data:
     - constitution.md
     - prd.md
@@ -65,7 +67,7 @@ You are Samira, a Scrum Master focused on creating implementation-ready stories
 
 ## Story Creation Workflow
 
-### Phase 1: Context Gathering
+### 1. Context Gathering (Path A: Greenfield)
 
 ```
 1. Read Planning Phase Outputs
@@ -73,21 +75,23 @@ You are Samira, a Scrum Master focused on creating implementation-ready stories
    - Architecture doc (from Architect)
    - Epic definition
    - Related stories
+```
 
-2. Shard Epic if Needed
-   - If epic > 40 story points: shard into smaller epics
-   - Each shard: 20-40 points (1-2 weeks)
-   - Save shards to epic-shards/{epic}-shard-{N}.md
+### 2. Task Breakdown (Path B: OpenSpec)
 
-3. Query mem0 for Context
-   /mem0 retrieve story context <epic>
-   /mem0 retrieve implementation notes <feature>
+```
+1. Read Change Context
+   - Proposal (from PM) in `openspec/changes/<name>/proposal.md`
+   - Spec Deltas (from Architect) in `openspec/changes/<name>/specs/delta.md`
 
-4. Use Context7 for Patterns
-   @context7 <relevant technology>
+2. Create Implementation Tasks
+   - Create/Update `openspec/changes/<name>/tasks.md`
+   - Break down deltas into atomic TDD steps
+   - Ensure specific test guidance for each task
+   - Validate against Constitutional principles
 ```
 
-### Phase 2: Story Drafting
+### 3. Story Drafting
 
 ```
 1. Story Structure
@@ -722,7 +726,7 @@ test('complete login flow', async () => {
 - [ ] Risk assessment included
 - [ ] Dependencies identified
 - [ ] Performance requirements defined
-- [ ] Security requirements included
+- [ ] Security requirements defined
 - [ ] Definition of Done complete
 - [ ] Story points estimated
 - [ ] Constitutional compliance verified
@@ -780,5 +784,5 @@ Would you like me to:
 ---
 
 **Agent Version**: 1.0.0
-**Framework**: AgentDevFramework-Claude
-**Methodology**: BMAD-METHOD + Context Engineering + Agile Best Practices
+**Framework**: AgentDevFramework
+**Methodology**: BMAD-METHOD + Context Engineering + Agile Best Practices

package/lib/templates/shared/templates/openspec-delta.md

@@ -0,0 +1,16 @@
+# OpenSpec Delta: [Spec Name]
+
+## ➕ ADDED Requirements
+### Requirement: [Name]
+Description using SHALL/MUST.
+#### Scenario: [Context]
+- WHEN [Action]
+- THEN [Outcome]
+
+## 🔄 MODIFIED Requirements
+### Requirement: [Name]
+*Original requirement reference*
+Updated description.
+
+## ➖ REMOVED Requirements
+- [Requirement Name]

package/lib/templates/shared/templates/openspec-proposal.md

@@ -0,0 +1,18 @@
+# OpenSpec Change Proposal: [Feature Name]
+
+## 🎯 Purpose
+Briefly describe WHY this change is needed and what problem it solves.
+
+## 📝 Proposed Changes
+High-level summary of the functional changes.
+
+## 🗄️ Technical Approach
+- Architecture decisions
+- Impacted components
+- New dependencies (if any)
+
+## 🚧 Verification Plan
+- [ ] Syntax check
+- [ ] Unit tests
+- [ ] Integration tests
+- [ ] Manual verification

package/lib/templates/shared/templates/openspec-tasks.md

@@ -0,0 +1,21 @@
+# OpenSpec Implementation Tasks: [Feature Name]
+
+## 🛠️ Task Breakdown
+
+### Phase 1: Setup & Infrastructure
+- [ ] 1.1 Task Description
+- [ ] 1.2 Task Description
+
+### Phase 2: Implementation
+- [ ] 2.1 Task Description
+- [ ] 2.2 Task Description
+
+### Phase 3: Testing & Validation
+- [ ] 3.1 Task Description
+- [ ] 3.2 Task Description
+
+## ✅ Definition of Done
+- All tasks marked complete
+- Tests passing (>80% coverage)
+- Documentation updated
+- Change ready for archive