aios-core 1.0.0

package/.aios-core/schemas/squad-schema.json

@@ -0,0 +1,185 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "https://github.com/SynkraAI/aios-core/schemas/squad-schema.json",
+  "title": "AIOS Squad Manifest",
+  "description": "Schema for squad.yaml manifest files (Task-First Architecture)",
+  "type": "object",
+  "required": ["name", "version"],
+  "properties": {
+    "name": {
+      "type": "string",
+      "pattern": "^[a-z0-9-]+$",
+      "description": "Squad name in kebab-case (e.g., my-squad-name)",
+      "minLength": 2,
+      "maxLength": 50
+    },
+    "version": {
+      "type": "string",
+      "pattern": "^\\d+\\.\\d+\\.\\d+$",
+      "description": "Semantic version (e.g., 1.0.0)"
+    },
+    "short-title": {
+      "type": "string",
+      "maxLength": 100,
+      "description": "Short title for the squad"
+    },
+    "description": {
+      "type": "string",
+      "maxLength": 500,
+      "description": "Brief description of the squad's purpose"
+    },
+    "author": {
+      "type": "string",
+      "description": "Author name or organization"
+    },
+    "license": {
+      "type": "string",
+      "enum": ["MIT", "Apache-2.0", "ISC", "GPL-3.0", "UNLICENSED"],
+      "default": "MIT",
+      "description": "License type"
+    },
+    "slashPrefix": {
+      "type": "string",
+      "pattern": "^[a-z0-9-]+$",
+      "description": "Prefix for slash commands (e.g., 'etl' for /etl-*)"
+    },
+    "aios": {
+      "type": "object",
+      "properties": {
+        "minVersion": {
+          "type": "string",
+          "pattern": "^\\d+\\.\\d+\\.\\d+$",
+          "description": "Minimum AIOS version required"
+        },
+        "type": {
+          "type": "string",
+          "enum": ["squad"],
+          "description": "Must be 'squad'"
+        }
+      }
+    },
+    "requires": {
+      "type": "object",
+      "description": "Runtime requirements",
+      "properties": {
+        "node": {
+          "type": "string",
+          "description": "Node.js version requirement (e.g., >=18.0.0)"
+        },
+        "aios": {
+          "type": "string",
+          "description": "AIOS version requirement (e.g., >=2.0.0)"
+        }
+      }
+    },
+    "tags": {
+      "type": "array",
+      "items": { "type": "string" },
+      "description": "Keywords for discovery"
+    },
+    "components": {
+      "type": "object",
+      "description": "Task-first: tasks are primary entry point",
+      "properties": {
+        "tasks": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "List of task files (primary - task-first!)"
+        },
+        "agents": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "List of agent definition files"
+        },
+        "workflows": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "List of workflow files"
+        },
+        "checklists": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "List of checklist files"
+        },
+        "templates": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "List of template files"
+        },
+        "tools": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "List of tool scripts"
+        },
+        "scripts": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "List of automation scripts"
+        }
+      }
+    },
+    "scripts": {
+      "type": "object",
+      "description": "Script definitions organized by category",
+      "additionalProperties": {
+        "type": "array",
+        "items": { "type": "string" }
+      }
+    },
+    "config": {
+      "type": "object",
+      "description": "Configuration inheritance from aios-core",
+      "properties": {
+        "extends": {
+          "type": "string",
+          "enum": ["extend", "override", "none"],
+          "default": "extend",
+          "description": "How to handle core config (extend adds rules, override replaces)"
+        },
+        "coding-standards": {
+          "type": "string",
+          "description": "Path to squad-specific coding standards (relative to squad root)"
+        },
+        "tech-stack": {
+          "type": "string",
+          "description": "Path to squad-specific tech stack doc"
+        },
+        "source-tree": {
+          "type": "string",
+          "description": "Path to squad-specific source tree doc"
+        }
+      }
+    },
+    "dependencies": {
+      "type": "object",
+      "properties": {
+        "node": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "Node.js package dependencies"
+        },
+        "python": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "Python package dependencies"
+        },
+        "squads": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "Other squads this depends on"
+        }
+      }
+    },
+    "mcps": {
+      "type": "object",
+      "description": "MCP server configurations",
+      "additionalProperties": true
+    },
+    "integration": {
+      "type": "object",
+      "description": "Integration configurations",
+      "additionalProperties": true
+    }
+  },
+  "additionalProperties": true
+}

package/.aios-core/scripts/README.md

@@ -0,0 +1,122 @@
+# AIOS Scripts - Legacy Directory
+
+> **Note**: This directory now contains only legacy/migration scripts and a few active utilities.
+> Most scripts have been migrated to the modular structure (Story 6.16).
+
+## Current Structure
+
+Scripts are now organized by domain across three locations:
+
+| Location | Purpose |
+|----------|---------|
+| `.aios-core/core/` | Core framework modules (elicitation, session) |
+| `.aios-core/development/scripts/` | Development scripts (greeting, workflow, hooks) |
+| `.aios-core/infrastructure/scripts/` | Infrastructure scripts (git config, validators) |
+| `.aios-core/scripts/` (this directory) | Legacy utilities and migration scripts |
+
+## Scripts in This Directory
+
+### Active Scripts
+
+| Script | Description |
+|--------|-------------|
+| `session-context-loader.js` | Loads session context for agents |
+| `command-execution-hook.js` | Hook for command execution |
+| `test-template-system.js` | Internal test utility for templates |
+
+### Migration Scripts
+
+| Script | Description |
+|--------|-------------|
+| `batch-migrate-*.ps1` | Batch migration utilities |
+| `migrate-framework-docs.sh` | Documentation migration script |
+| `validate-phase1.ps1` | Phase 1 validation script |
+
+## Script Path Mapping
+
+If you're looking for a script that was previously here, use this mapping:
+
+```text
+OLD PATH                                      NEW PATH
+-----------------------------------------     ------------------------------------------
+.aios-core/scripts/context-detector.js      → .aios-core/core/session/context-detector.js
+.aios-core/scripts/elicitation-engine.js    → .aios-core/core/elicitation/elicitation-engine.js
+.aios-core/scripts/elicitation-session-manager.js → .aios-core/core/elicitation/session-manager.js
+.aios-core/scripts/greeting-builder.js      → .aios-core/development/scripts/greeting-builder.js
+.aios-core/scripts/workflow-navigator.js    → .aios-core/development/scripts/workflow-navigator.js
+.aios-core/scripts/agent-exit-hooks.js      → .aios-core/development/scripts/agent-exit-hooks.js
+.aios-core/scripts/git-config-detector.js   → .aios-core/infrastructure/scripts/git-config-detector.js
+.aios-core/scripts/project-status-loader.js → .aios-core/infrastructure/scripts/project-status-loader.js
+.aios-core/scripts/aios-validator.js        → .aios-core/infrastructure/scripts/aios-validator.js
+.aios-core/scripts/tool-resolver.js         → .aios-core/infrastructure/scripts/tool-resolver.js
+.aios-core/scripts/output-formatter.js      → .aios-core/infrastructure/scripts/output-formatter.js
+```
+
+## Configuration
+
+The `scriptsLocation` in `core-config.yaml` now uses a modular structure:
+
+```yaml
+scriptsLocation:
+  core: .aios-core/core
+  development: .aios-core/development/scripts
+  infrastructure: .aios-core/infrastructure/scripts
+  legacy: .aios-core/scripts  # This directory
+```
+
+## Usage Examples
+
+### Loading Core Scripts
+
+```javascript
+// Elicitation Engine (from core)
+const ElicitationEngine = require('./.aios-core/core/elicitation/elicitation-engine');
+
+// Context Detector (from core)
+const ContextDetector = require('./.aios-core/core/session/context-detector');
+```
+
+### Loading Development Scripts
+
+```javascript
+// Greeting Builder
+const GreetingBuilder = require('./.aios-core/development/scripts/greeting-builder');
+
+// Workflow Navigator
+const WorkflowNavigator = require('./.aios-core/development/scripts/workflow-navigator');
+```
+
+### Loading Infrastructure Scripts
+
+```javascript
+// Project Status Loader
+const { loadProjectStatus } = require('./.aios-core/infrastructure/scripts/project-status-loader');
+
+// Git Config Detector
+const GitConfigDetector = require('./.aios-core/infrastructure/scripts/git-config-detector');
+```
+
+### Loading Legacy Scripts (this directory)
+
+```javascript
+// Session Context Loader
+const sessionLoader = require('./.aios-core/scripts/session-context-loader');
+```
+
+## Related Documentation
+
+- [Core Config](../core-config.yaml) - scriptsLocation configuration
+- [Core Module](../core/README.md) - Core framework modules
+- [Development Scripts](../development/scripts/README.md) - Development utilities
+- [Infrastructure Scripts](../infrastructure/scripts/README.md) - Infrastructure utilities
+
+## Migration History
+
+| Date | Story | Change |
+|------|-------|--------|
+| 2025-12-18 | 6.16 | Deleted deprecated scripts, updated documentation |
+| 2025-01-15 | 2.2 | Initial script reorganization to modular structure |
+
+---
+
+**Last updated:** 2025-12-18 - Story 6.16 Scripts Path Consolidation

package/.aios-core/scripts/aios-doc-template.md

@@ -0,0 +1,325 @@
+# AIOS Document Template Specification
+
+## Overview
+
+AIOS document templates are defined in YAML format to drive interactive document generation and agent interaction. Templates separate structure definition from content generation, making them both human and LLM-agent-friendly.
+
+## Template Structure
+
+```yaml
+template:
+  id: template-identifier
+  name: Human Readable Template Name
+  version: 1.0
+  output:
+    format: markdown
+    filename: default-path/to/{{filename}}.md
+    title: "{{variable}} Document Title"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+sections:
+  - id: section-id
+    title: Section Title
+    instruction: |
+      Detailed instructions for the LLM on how to handle this section
+    # ... additional section properties
+```
+
+## Core Fields
+
+### Template Metadata
+
+- **id**: Unique identifier for the template
+- **name**: Human-readable name displayed in UI
+- **version**: Template version for tracking changes
+- **output.format**: Default "markdown" for document templates
+- **output.filename**: Default output file path (can include variables)
+- **output.title**: Document title (becomes H1 in markdown)
+
+### Workflow Configuration
+
+- **workflow.mode**: Default interaction mode ("interactive" or "yolo")
+- **workflow.elicitation**: Elicitation task to use ("advanced-elicitation")
+
+## Section Properties
+
+### Required Fields
+
+- **id**: Unique section identifier
+- **title**: Section heading text
+- **instruction**: Detailed guidance for LLM on handling this section
+
+### Optional Fields
+
+#### Content Control
+
+- **type**: Content type hint for structured sections
+- **template**: Fixed template text for section content
+- **item_template**: Template for repeatable items within section
+- **prefix**: Prefix for numbered items (e.g., "FR", "NFR")
+
+#### Behavior Flags
+
+- **elicit**: Boolean - Apply elicitation after section rendered
+- **repeatable**: Boolean - Section can be repeated multiple times
+- **condition**: String - Condition for including section (e.g., "has ui requirements")
+
+#### Agent Permissions
+
+- **owner**: String - Agent role that initially creates/populates this section
+- **editors**: Array - List of agent roles allowed to modify this section
+- **readonly**: Boolean - Section cannot be modified after initial creation
+
+#### Content Guidance
+
+- **examples**: Array of example content (not included in output)
+- **choices**: Object with choice options for common decisions
+- **placeholder**: Default placeholder text
+
+#### Structure
+
+- **sections**: Array of nested child sections
+
+## Supported Types
+
+### Content Types
+
+- **bullet-list**: Unordered list items
+- **numbered-list**: Ordered list with optional prefix
+- **paragraphs**: Free-form paragraph text
+- **table**: Structured table data
+- **code-block**: Code or configuration blocks
+- **template-text**: Fixed template with variable substitution
+- **mermaid**: Mermaid diagram with specified type and details
+
+### Special Types
+
+- **repeatable-container**: Container for multiple instances
+- **conditional-block**: Content shown based on conditions
+- **choice-selector**: Present choices to user
+
+## Advanced Features
+
+### Variable Substitution
+
+Use `{{variable_name}}` in titles, templates, and content:
+
+```yaml
+title: "Epic {{epic_number}} {{epic_title}}"
+template: "As a {{user_type}}, I want {{action}}, so that {{benefit}}."
+```
+
+### Conditional Sections
+
+```yaml
+- id: ui-section
+  title: User Interface Design
+  condition: Project has UX/UI Requirements
+  instruction: Only include if project has UI components
+```
+
+### Choice Integration
+
+```yaml
+choices:
+  architecture: [Monolith, Microservices, Serverless]
+  testing: [Unit Only, Unit + Integration, Full Pyramid]
+```
+
+### Mermaid Diagrams
+
+```yaml
+- id: system-architecture
+  title: System Architecture Diagram
+  type: mermaid
+  instruction: Create a system architecture diagram showing key components and data flow
+  mermaid_type: flowchart
+  details: |
+    Show the following components:
+    - User interface layer
+    - API gateway
+    - Core services
+    - Database layer
+    - External integrations
+```
+
+**Supported mermaid_type values:**
+
+**Core Diagram Types:**
+
+- `flowchart` - Flow charts and process diagrams
+- `sequenceDiagram` - Sequence diagrams for interactions
+- `classDiagram` - Class relationship diagrams (UML)
+- `stateDiagram` - State transition diagrams
+- `erDiagram` - Entity relationship diagrams
+- `gantt` - Gantt charts for timelines
+- `pie` - Pie charts for data visualization
+
+**Advanced Diagram Types:**
+
+- `journey` - User journey maps
+- `mindmap` - Mindmaps for brainstorming
+- `timeline` - Timeline diagrams for chronological events
+- `quadrantChart` - Quadrant charts for data categorization
+- `xyChart` - XY charts (bar charts, line charts)
+- `sankey` - Sankey diagrams for flow visualization
+
+**Specialized Types:**
+
+- `c4Context` - C4 context diagrams (experimental)
+- `requirement` - Requirement diagrams
+- `packet` - Network packet diagrams
+- `block` - Block diagrams
+- `kanban` - Kanban boards
+
+### Agent Permissions Example
+
+```yaml
+- id: story-details
+  title: Story
+  owner: scrum-master
+  editors: [scrum-master]
+  readonly: false
+  sections:
+    - id: dev-notes
+      title: Dev Notes
+      owner: dev-agent
+      editors: [dev-agent]
+      readonly: false
+      instruction: Implementation notes and technical details
+    - id: qa-results
+      title: QA Results
+      owner: qa-agent
+      editors: [qa-agent]
+      readonly: true
+      instruction: Quality assurance test results
+```
+
+### Repeatable Sections
+
+```yaml
+- id: epic-details
+  title: Epic {{epic_number}} {{epic_title}}
+  repeatable: true
+  sections:
+    - id: story
+      title: Story {{epic_number}}.{{story_number}} {{story_title}}
+      repeatable: true
+      sections:
+        - id: criteria
+          title: Acceptance Criteria
+          type: numbered-list
+          item_template: "{{criterion_number}}: {{criteria}}"
+          repeatable: true
+```
+
+### Examples with Code Blocks
+
+````yaml
+examples:
+  - "FR6: The system must authenticate users within 2 seconds"
+  - |
+    ```mermaid
+    sequenceDiagram
+        participant User
+        participant API
+        participant DB
+        User->>API: POST /login
+        API->>DB: Validate credentials
+        DB-->>API: User data
+        API-->>User: JWT token
+    ```
+  - |
+    **Architecture Decision Record**
+
+    **Decision**: Use PostgreSQL for primary database
+    **Rationale**: ACID compliance and JSON support needed
+    **Consequences**: Requires database management expertise
+````
+
+## Section Hierarchy
+
+Templates define the complete document structure starting with the first H2 - each level in is the next H#:
+
+```yaml
+sections:
+  - id: overview
+    title: Project Overview
+    sections:
+      - id: goals
+        title: Goals
+      - id: scope
+        title: Scope
+        sections:
+          - id: in-scope
+            title: In Scope
+          - id: out-scope
+            title: Out of Scope
+```
+
+## Processing Flow
+
+1. **Parse Template**: Load and validate YAML structure
+2. **Initialize Workflow**: Set interaction mode and elicitation
+3. **Process Sections**: Handle each section in order:
+   - Check conditions
+   - Apply instructions
+   - Generate content
+   - Handle choices and variables
+   - Apply elicitation if specified
+   - Process nested sections
+4. **Generate Output**: Create clean markdown document
+
+## Best Practices
+
+### Template Design
+
+- Keep instructions clear and specific
+- Use examples for complex content
+- Structure sections logically
+- Include all necessary guidance for LLM
+
+### Content Instructions
+
+- Be explicit about expected format
+- Include reasoning for decisions
+- Specify interaction patterns
+- Reference other documents when needed
+
+### Variable Naming
+
+- Use descriptive variable names
+- Follow consistent naming conventions
+- Document expected variable values
+
+### Examples Usage
+
+- Provide concrete examples for complex sections
+- Include both simple and complex cases
+- Use realistic project scenarios
+- Include code blocks and diagrams when helpful
+
+## Validation
+
+Templates should be validated for:
+
+- Valid YAML syntax
+- Required fields present
+- Consistent section IDs
+- Proper nesting structure
+- Valid variable references
+
+## Migration from Legacy
+
+When converting from markdown+frontmatter templates:
+
+1. Extract embedded `[[LLM:]]` instructions to `instruction` fields
+2. Convert `<<REPEAT>>` blocks to `repeatable: true` sections
+3. Extract `^^CONDITIONS^^` to `condition` fields
+4. Move `@{examples}` to `examples` arrays
+5. Convert `{{placeholders}}` to proper variable syntax
+
+This specification ensures templates are both human-readable and machine-processable while maintaining the flexibility needed for complex document generation.

package/.aios-core/scripts/batch-migrate-phase1.ps1

@@ -0,0 +1,36 @@
+# Phase 1 - Batch migrate critical tasks
+
+$tasks = @(
+  'create-next-story.md',
+  'brownfield-create-story.md', 
+  'brownfield-create-epic.md',
+  'create-agent.md',
+  'modify-agent.md',
+  'create-task.md',
+  'qa-gate.md',
+  'qa-test-design.md',
+  'execute-checklist.md',
+  'correct-course.md',
+  'create-doc.md',
+  'shard-doc.md'
+)
+
+$successCount = 0
+$failCount = 0
+
+foreach ($task in $tasks) {
+  Write-Host "`n=== Migrating $task ===" -ForegroundColor Cyan
+  node .aios-core/scripts/migrate-task-to-v2.js ".aios-core/tasks/$task"
+  
+  if ($LASTEXITCODE -eq 0 -or $LASTEXITCODE -eq 1) {
+    $successCount++
+  } else {
+    $failCount++
+    Write-Host "Failed to migrate $task" -ForegroundColor Red
+  }
+}
+
+Write-Host "`n=== Phase 1 Migration Complete ===" -ForegroundColor Green
+Write-Host "Success: $successCount" -ForegroundColor Green
+Write-Host "Failed: $failCount" -ForegroundColor $(if ($failCount -gt 0) { 'Red' } else { 'Green' })
+