ce-workflow 0.4.0

package/agent-core/prompts/sync.md

@@ -0,0 +1,48 @@
+---
+name: CE-Workflow Sync
+description: Reconcile project state with the CE-Workflow knowledge base and update semantic index.
+argument-hint: "[SCOPE=<path|module>]"
+tools: ['resolve_path', 'get_context_bundle', 'search_knowledge', 'search_code', 'get_project_context', 'index_knowledge', 'list_projects', 'update_task', 'read', 'write', 'glob', 'grep']
+required-args: []
+optional-args:
+  - name: SCOPE
+    default: ""
+auto-identity:
+  user: "$GIT_USER"
+  model: "$AGENT_MODEL"
+---
+
+You are the Knowledge Sync Lead. Act like a senior architect charged with keeping the CE-Workflow knowledge cache authoritative and current.
+
+## Pipeline Position
+- **Maintenance Agent**: Runs periodically or after significant codebase changes
+- **Requires**: Init must have been run at least once (`project-context.md` must exist)
+- **Triggers Init**: If major structural changes detected, recommend running `/init`
+
+## Prerequisites (STRICT)
+Check `{{CE_DATA}}/knowledge/project-context.md` exists.
+- If missing: "Project context not found. Please run `/init` first."
+
+## Mission
+- Inspect the live codebase to understand the present implementation and recent changes
+- Align the knowledge base so every entry reflects the latest reality
+
+Non-Negotiables
+1. Perform your own discovery; read source files, configs, and docs directly—do not rely on prior summaries.
+2. Cross-check each relevant knowledge entry against the code. Update, merge, or delete content so no contradictions remain.
+3. Version every knowledge edit by stamping an ISO date (e.g. `Updated: 2024-11-01`) near the top of the section you modify.
+4. Keep all knowledge files lean (<500 lines each) and focused on durable insights, linking to code paths or task artifacts instead of duplicating detail.
+5. Record gaps or follow-up items in a checklist inside the file you touched so future runs can close them.
+6. **Semantic Indexing (MANDATORY)**: After updating any knowledge files, run the indexer to keep search current.
+
+## Reindexing Guidance
+
+| Scenario | Tool Argument | Rationale |
+|----------|---------------|-----------|
+| Routine updates | `{ "project": "{{WORKSPACE_NAME}}" }` | Incremental (fastest). Only updates changed files. |
+| Major refactors | `{ "project": "{{WORKSPACE_NAME}}", "force": true }` | Forces re-calculation of hashes for all files without wiping. |
+| Corrupt index / Stale vectors | `{ "project": "{{WORKSPACE_NAME}}", "clean": true }` | Wipes index files and rebuilds from scratch. Resolves vector drift. |
+
+Deliverable
+- Updated `{{CE_DATA}}/knowledge/*` files that accurately reflect the present project state, each carrying the latest `Updated:` marker and lean checklist.
+- Optional supporting notes saved alongside the knowledge files if deeper context is required; keep these under 500 lines as well.

package/agent-core/templates/docs/.gitkeep

@@ -0,0 +1 @@
+

package/agent-core/templates/doctor_output.md

@@ -0,0 +1,138 @@
+<!--
+  TEMPLATE: Project Diagnosis
+  
+  HOW TO USE:
+  1. Copy to: {{CE_DATA}}/tasks/doctor-{{YYYYMMDD}}/diagnosis.md
+  2. Replace {{variable}} placeholders with actual values
+  3. Add findings under appropriate priority sections
+  4. Remove empty sections and placeholder rows
+  
+  SYSTEM PATH VARIABLES (Must be replaced by agent using System Resolved Paths):
+  - {{CE_DATA}}: Storage path for knowledge/tasks (Use value from system context!)
+  - {{WORKSPACE_ROOT}}: Source code directory
+  
+  AGENT-FILLED VARIABLES:
+  - {{project_name}}: Name of the project
+  - {{date}}: ISO date (YYYY-MM-DD)
+  - {{author}}: Git user or agent name (analyst)
+  - {{workspace_root}}: Source code directory
+  - {{focus_area}}: Focus area parameter or "General"
+-->
+# Project Diagnosis – {{project_name}}
+
+- Diagnosis Date: `{{date}}`
+- Analyst: `{{author}}`
+- Workspace: `{{workspace_root}}`
+- Focus Area: `{{focus_area}}` (or "General" if not specified)
+- Project Context: `{{CE_DATA}}/knowledge/project-context.md`
+
+---
+
+## Executive Summary
+
+A brief 2-3 sentence summary of the overall codebase health and most critical findings.
+
+---
+
+## Health Score
+
+| Category | Score (1-5) | Notes |
+|----------|-------------|-------|
+| Code Quality |  |  |
+| Architecture |  |  |
+| Testing |  |  |
+| Security |  |  |
+| Performance |  |  |
+| Maintainability |  |  |
+| **Overall** |  |  |
+
+*Scale: 1=Critical issues, 2=Significant issues, 3=Acceptable, 4=Good, 5=Excellent*
+
+---
+
+## Critical Findings (P0-P1)
+
+### Finding 1: [Title]
+- **Category**: (Code Quality / Architecture / Testing / Security / Performance)
+- **Priority**: P0 / P1
+- **Impact**: High
+- **Effort**: Low / Medium / High
+- **Location**: `path/to/file.ts:L42-L100`
+- **Description**: What is the problem?
+- **Evidence**: Code snippets, metrics, or specific examples.
+- **Recommendation**: What should be done?
+- **Acceptance Criteria**:
+  - [ ] Criterion 1
+  - [ ] Criterion 2
+
+---
+
+## Medium Priority Findings (P2)
+
+### Finding N: [Title]
+- **Category**: 
+- **Priority**: P2
+- **Impact**: Medium
+- **Effort**: 
+- **Description**: 
+- **Recommendation**: 
+
+---
+
+## Low Priority / Backlog (P3+)
+
+| Finding | Category | Effort | Notes |
+|---------|----------|--------|-------|
+|  |  |  |  |
+
+---
+
+## Recommended Tasks for Planning Agent
+
+> These are ready-to-use task definitions for the `planning` agent.
+
+### Task 1: [Suggested Title]
+```yaml
+title: "[ACTION] [COMPONENT]: [Goal]"
+priority: P1
+category: refactoring / bugfix / feature / docs
+description: |
+  Brief description of what needs to be done and why.
+acceptance_criteria:
+  - Criterion 1
+  - Criterion 2
+estimated_effort: "2-4 hours / 1-2 days / 1 week"
+dependencies:
+  - Any blocking tasks or requirements
+context_artifacts:
+  - "{{CE_DATA}}/knowledge/project-context.md"
+  - "path/to/relevant/file.ts"
+```
+
+### Task 2: [Suggested Title]
+```yaml
+# ... repeat format
+```
+
+---
+
+## Metrics & Data
+
+Any relevant metrics collected during analysis:
+- Lines of code: 
+- Files analyzed: 
+- Test coverage (if available): 
+- Dependency count: 
+- TODO/FIXME comments found: 
+
+---
+
+## Next Steps
+
+1. Review findings with team/stakeholder
+2. Hand off high-priority tasks to `planning` agent: `ce-workflow run planning --task="<Task Title>"`
+3. Schedule follow-up diagnosis in: [timeframe]
+
+---
+
+> This diagnosis is based on automated analysis and code review. Human judgment should validate recommendations before implementation.

package/agent-core/templates/documentation_output.md

@@ -0,0 +1,71 @@
+<!--
+  TEMPLATE: Handover Note / Documentation
+  
+  HOW TO USE:
+  1. Copy to destination based on DOC_TYPE:
+     - With TASK_SLUG: {{CE_DATA}}/tasks/{{TASK_SLUG}}/docs/{{TASK_SLUG}}-{{DOC_TYPE}}.md
+     - With TARGET_PATH: {{CE_DATA}}/{{TARGET_PATH}}
+     - Default: {{CE_DATA}}/knowledge/{{DOC_TYPE}}.md
+  2. Replace {{variable}} placeholders with actual values
+  3. Remove empty sections
+  
+  SYSTEM PATH VARIABLES (Must be replaced by agent using System Resolved Paths):
+  - {{CE_DATA}}: Storage path for knowledge/tasks (Use value from system context!)
+  - {{WORKSPACE_NAME}}: Project name
+  
+  AGENT-FILLED VARIABLES:
+  - {{task_id}}: UUID for the task (if applicable)
+  - {{task_slug}}: kebab-case task identifier (if applicable)
+  - {{task_title}}: Human-readable task title
+  - {{author}}: Git user or agent name
+  - {{date}}: ISO date (YYYY-MM-DD)
+  - {{execution_artifact}}: Path to execution log
+  - {{release_ref}}: Release tag or commit SHA
+  - {{workspace_name}}: Project name
+-->
+# Handover Note – {{task_title}}
+
+- Task ID: `{{task_id}}`
+- Task Slug: `{{task_slug}}`
+- Author: `{{author}}`
+- Date: `{{date}}`
+- Execution Artifact: `{{execution_artifact}}`
+- Release / Merge Reference: `{{release_ref}}`
+- Workspace: `{{workspace_name}}`
+
+## 1. Overview
+- Purpose of the work and high-level outcome.
+- Linked research, plan, and execution documents.
+
+## Checklist
+- [ ] Replace with sign-off requirement.
+- [ ] Replace with follow-up confirmation.
+
+## 2. Implementation Details
+- Summary of major code changes and affected components.
+- Feature flags, configuration updates, or migrations.
+
+## 3. Validation Evidence
+- Tests executed and results.
+- Monitoring or telemetry instructions post-release.
+
+## 4. Decisions & Rationale
+- Final decisions made with references.
+- Deferred items or future considerations.
+
+## 5. Knowledge Sync
+- Updates pushed to `{{CE_DATA}}/knowledge` with file references.
+- External documentation or runbooks updated.
+
+## 6. Operational Notes
+- Deployment steps, rollback plan, and ownership.
+- Support contacts or escalation paths.
+
+## 7. Follow-up Actions
+- Outstanding tasks or bugs.
+- Recommendations for future improvements.
+
+## 8. Sign-off
+- Confirmation of readiness and any approvals obtained.
+
+> Keep this handover document under 500 lines. Ensure all links are relative paths when possible.

package/agent-core/templates/executor_output.md

@@ -0,0 +1,64 @@
+<!--
+  TEMPLATE: Execution Log
+  
+  HOW TO USE:
+  1. Copy to: {{CE_DATA}}/tasks/{{TASK_SLUG}}/execution/{{TASK_SLUG}}-execution.md
+  2. Replace {{variable}} placeholders with actual values
+  3. Update Implementation Steps table as work progresses
+  4. Remove empty sections
+  
+  SYSTEM PATH VARIABLES (Must be replaced by agent using System Resolved Paths):
+  - {{CE_DATA}}: Storage path for knowledge/tasks (Use value from system context!)
+  - {{WORKSPACE_NAME}}: Project name
+  
+  AGENT-FILLED VARIABLES:
+  - {{task_id}}: UUID for the task
+  - {{task_slug}}: kebab-case task identifier
+  - {{task_title}}: Human-readable task title
+  - {{author}}: Git user or agent name (executor)
+  - {{date}}: ISO date (YYYY-MM-DD)
+  - {{plan_artifact}}: Path to execution plan
+  - {{git_ref}}: Branch name or commit SHA
+  - {{workspace_name}}: Project name
+-->
+# Execution Log – {{task_title}}
+
+- Task ID: `{{task_id}}`
+- Task Slug: `{{task_slug}}`
+- Executor: `{{author}}`
+- Date: `{{date}}`
+- Plan Artifact: `{{plan_artifact}}`
+- Branch / Commit Reference: `{{git_ref}}`
+- Workspace: `{{workspace_name}}`
+
+## 1. Work Summary
+- Brief narrative of what was completed.
+- Note any deviations from the plan and why.
+
+## Checklist
+- [ ] Replace with implementation task item.
+- [ ] Replace with verification checkpoint.
+
+## 2. Implementation Steps
+| Step | Description | Status | Evidence / Links |
+| --- | --- | --- | --- |
+| 1 |  | pending |  |
+
+## 3. Testing & Verification
+- Commands executed (summaries only) and outcomes.
+- Coverage of automated and manual checks.
+- Outstanding testing gaps, if any.
+
+## 4. Issues & Follow-ups
+- Bugs discovered, blocked tasks, escalations.
+- Required clarifications for future cycles.
+
+## 5. Deliverables
+- Key files, PRs, or artifacts delivered.
+- Documentation or knowledge updates triggered.
+
+## 6. Next Actions
+- Items remaining before handoff or release.
+- Recommendations for the Documentation agent.
+
+> Keep this log under 500 lines. Inline only the essential evidence; link to detailed outputs when needed.

package/agent-core/templates/init_output.md

@@ -0,0 +1,307 @@
+<!--
+  TEMPLATE: Project Context (Init Output)
+  
+  HOW TO USE:
+  1. Copy to: {{CE_DATA}}/knowledge/project-context.md
+  2. Replace {{variable}} placeholders with actual values
+  3. Delete sections marked (OPTIONAL) if empty after population
+  4. Fill in remaining sections with discovered information
+  
+  SYSTEM PATH VARIABLES (Must be replaced by agent using System Resolved Paths):
+  - {{WORKSPACE_ROOT}}: Source code directory
+  - {{WORKSPACE_NAME}}: Project name  
+  - {{CE_DATA}}: Storage path for knowledge/tasks (Use value from system context!)
+  - {{CE_HOME}}: Global CE-Workflow home directory
+  
+  AGENT-FILLED VARIABLES:
+  - {{project_name}}: Name of the project
+  - {{date}}: ISO date (YYYY-MM-DD)
+  - {{author}}: Git user or agent name
+  - {{workspace_root}}: Same as WORKSPACE_ROOT
+  
+  DYNAMIC VARIABLES:
+  - {{test_unit_command}}: Command to run unit tests
+  - {{test_integration_command}}: Command to run integration tests
+  - {{test_e2e_command}}: Command to run e2e tests
+  - {{coverage_command}}: Command to generate coverage report
+  - {{last_indexed_date}}: Last semantic index update
+  - {{index_path}}: Path to embeddings.json
+-->
+# Project Context – {{project_name}}
+
+- Initialized: `{{date}}`
+- Last Updated: `{{date}}`
+- Author: `{{author}}`
+- Workspace: `{{workspace_root}}`
+
+---
+
+## 1. Project Identity
+
+| Attribute | Value |
+|-----------|-------|
+| **Name** |  |
+| **Description** |  |
+| **Primary Language(s)** |  |
+| **Runtime Version(s)** |  |
+| **Repository Type** | monorepo / single-app / library |
+| **License** |  |
+
+### Key Documentation
+- README: 
+- CONTRIBUTING: 
+- Other: 
+
+---
+
+## 2. Tech Stack
+
+### Languages & Runtimes
+| Language | Version | Purpose |
+|----------|---------|---------|
+|  |  |  |
+
+### Frameworks
+| Framework | Version | Layer |
+|-----------|---------|-------|
+|  |  | frontend / backend / cli / mobile |
+
+### Databases & Storage
+| Technology | Purpose |
+|------------|---------|
+|  |  |
+
+### External Services & APIs
+| Service | Purpose | Auth Method |
+|---------|---------|-------------|
+|  |  |  |
+
+### Build Tools
+| Tool | Config File | Purpose |
+|------|-------------|---------|
+|  |  |  |
+
+---
+
+## 3. Code Organization
+
+### Directory Structure
+```
+{{workspace_root}}/
+├── 
+├── 
+└── 
+```
+
+### Structure Pattern
+- [ ] Monorepo (multiple packages/services)
+- [ ] Modular (feature-based organization)
+- [ ] Layered (controllers/services/repositories)
+- [ ] Flat (minimal nesting)
+- [ ] Other: 
+
+### Key Directories
+| Directory | Purpose |
+|-----------|---------|
+| `src/` |  |
+| `tests/` |  |
+| `docs/` |  |
+
+### Entry Points
+| File | Purpose |
+|------|---------|
+|  |  |
+
+---
+
+## 4. Coding Conventions
+
+### Style & Formatting
+| Tool | Config File | Key Rules |
+|------|-------------|-----------|
+| Linter |  |  |
+| Formatter |  |  |
+| Type Checker |  |  |
+
+### Naming Conventions
+| Element | Convention | Example |
+|---------|------------|---------|
+| Files |  |  |
+| Functions |  |  |
+| Classes |  |  |
+| Variables |  |  |
+| Constants |  |  |
+
+### Patterns Observed
+- **Error Handling**: 
+- **State Management**: 
+- **Async Patterns**: 
+- **Logging**: 
+- **Configuration**: 
+- **Code Quality Gates**: 
+- [ ] Type checking enforced
+- [ ] Lint checks in CI
+- [ ] Code review required
+- [ ] Commit message conventions
+
+---
+
+## 5. Testing Strategy
+
+### Test Frameworks
+| Framework | Purpose | Config |
+|-----------|---------|--------|
+|  | unit |  |
+|  | integration |  |
+|  | e2e |  |
+
+### Test Organization
+- [ ] Co-located with source (`*.test.ts` next to `*.ts`)
+- [ ] Separate `tests/` directory
+- [ ] Separate `__tests__/` directories
+- [ ] Other: 
+
+### Coverage Requirements
+| Metric | Target | Current |
+|--------|--------|---------|
+| Line Coverage |  |  |
+| Branch Coverage |  |  |
+
+### Test Commands
+```bash
+# Unit tests
+{{test_unit_command}}
+
+# Integration tests
+{{test_integration_command}}
+
+# E2E tests
+{{test_e2e_command}}
+
+# Coverage report
+{{coverage_command}}
+```
+
+---
+
+## 6. DevOps & Deployment
+
+### CI/CD
+| Platform | Config File | Triggers |
+|----------|-------------|----------|
+|  |  |  |
+
+### Containerization
+| Tool | Config File | Purpose |
+|------|-------------|---------|
+| Docker |  |  |
+| Compose |  |  |
+
+### Environments
+| Environment | URL/Access | Notes |
+|-------------|------------|-------|
+| Development |  |  |
+| Staging |  |  |
+| Production |  |  |
+
+### Infrastructure
+| Tool | Purpose |
+|------|---------|
+|  |  |
+
+---
+
+## 7. Dependencies & Constraints
+
+### Key Dependencies
+| Dependency | Version | Purpose | Critical? |
+|------------|---------|---------|-----------|
+|  |  |  | yes/no |
+
+### Version Strategy
+- [ ] Exact versions pinned
+- [ ] Semver ranges allowed
+- [ ] Lock file committed
+- [ ] Regular dependency updates
+
+### Constraints & Requirements
+- **Node/Runtime Version**: 
+- **OS Compatibility**: 
+- **Browser Support**: 
+- **Security Requirements**: 
+- **Performance Targets**: 
+
+---
+
+## 8. Skill Requirements (Executor Scope)
+
+Based on the tech stack analysis, the Executor agent should have proficiency in:
+
+### Required Skills
+- [ ] 
+- [ ] 
+- [ ] 
+
+### Preferred Skills
+- [ ] 
+- [ ] 
+
+### Out of Scope
+- 
+- 
+
+---
+
+## 9. Project Scope (Research Boundaries)
+
+### In Scope for Research
+- 
+- 
+
+### Out of Scope
+- 
+- 
+
+### Key Stakeholders
+| Role | Responsibility |
+|------|----------------|
+|  |  |
+
+---
+
+## 10. Open Questions & Gaps
+
+| Question | Priority | Notes |
+|----------|----------|-------|
+|  | high/medium/low |  |
+
+
+---
+
+## 11. Semantic Index Status
+
+| Attribute | Value |
+|-----------|-------|
+| **Enabled** | yes / no |
+| **Last Indexed** | `{{last_indexed_date}}` |
+| **Index Location** | `{{index_path}}` |
+| **Total Files** |  |
+| **Total Chunks** |  |
+
+*If semantic search is enabled, run `index_knowledge` to update the index after significant changes.*
+
+---
+
+## Checklist
+
+
+- [ ] Tech stack fully documented
+- [ ] Coding conventions captured
+- [ ] Testing strategy clear
+- [ ] DevOps pipeline understood
+- [ ] Skill requirements defined
+- [ ] Scope boundaries established
+
+---
+
+> Keep this document under 500 lines. Update when major changes occur. Run `ce-workflow sync` periodically to reconcile with codebase changes.

package/agent-core/templates/meta.template.json

@@ -0,0 +1,54 @@
+{
+  "task_id": "",
+  "task_slug": "",
+  "title": "",
+  "status": "draft",
+  "summary": "",
+  "workspace": {
+    "name": "",
+    "path": "",
+    "hash": ""
+  },
+  "created_at": "",
+  "updated_at": "",
+  "tags": [],
+  "checklist": [
+    {
+      "id": "",
+      "label": "",
+      "status": "pending",
+      "owner": "",
+      "notes": ""
+    }
+  ],
+  "references": [],
+  "open_questions": [],
+  "decisions": [],
+  "milestones": [],
+  "agents": {
+    "research": {
+      "owner": "",
+      "status": "pending",
+      "artifact": "",
+      "notes": ""
+    },
+    "planning": {
+      "owner": "",
+      "status": "pending",
+      "artifact": "",
+      "notes": ""
+    },
+    "executor": {
+      "owner": "",
+      "status": "pending",
+      "artifact": "",
+      "notes": ""
+    },
+    "documentation": {
+      "owner": "",
+      "status": "pending",
+      "artifact": "",
+      "notes": ""
+    }
+  }
+}