ce-workflow 0.4.0

package/agent-core/templates/orchestrator_output.md

@@ -0,0 +1,51 @@
+# CE-Workflow Orchestration Summary
+
+**Generated**: {{TIMESTAMP}}  
+**Orchestrator**: CE-Workflow Workflow Orchestrator  
+**Phases Executed**: {{PHASES_EXECUTED}}
+
+---
+
+## Workflow Execution Summary
+
+### Requested Work
+{{USER_REQUEST}}
+
+### Phases Completed
+
+{{#each PHASES}}
+#### {{PHASE_NAME}}
+
+**Status**: {{STATUS}}  
+**Artifact**: `{{ARTIFACT_PATH}}`  
+**Duration**: {{DURATION}}
+
+**Key Outcomes:**
+{{OUTCOMES}}
+
+**Next Steps:**
+{{NEXT_STEPS}}
+
+---
+
+{{/each}}
+
+## Overall Status
+
+**Completion**: {{COMPLETION_PERCENTAGE}}%  
+**Ready for Next Phase**: {{READY_FOR_NEXT}}
+
+### Artifacts Generated
+
+{{#each ARTIFACTS}}
+- [`{{PATH}}`]({{PATH}}) - {{DESCRIPTION}}
+{{/each}}
+
+### Recommendations
+
+{{RECOMMENDATIONS}}
+
+---
+
+**Session Complete**: {{SESSION_COMPLETE}}  
+**Return Summary**: {{RETURN_SUMMARY}}

package/agent-core/templates/planning_output.md

@@ -0,0 +1,190 @@
+<!--
+  TEMPLATE: Execution Plan
+  
+  HOW TO USE:
+  1. Copy to: {{CE_DATA}}/tasks/{{TASK_SLUG}}/planning/{{TASK_SLUG}}-plan.md
+  2. Replace {{variable}} placeholders with actual values
+  3. Remove unused table rows and 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 (planner)
+  - {{date}}: ISO date (YYYY-MM-DD)
+  - {{research_artifact}}: Path to research brief
+  - {{workspace_name}}: Project name
+  
+  NOTE: This document is the output of an interactive planning session.
+  The Planning agent collaborated with the user to break down requirements
+  into actionable tasks before this plan was finalized.
+-->
+# Execution Plan – {{task_title}}
+
+| Field | Value |
+|-------|-------|
+| Task ID | `{{task_id}}` |
+| Task Slug | `{{task_slug}}` |
+| Planner | `{{author}}` |
+| Date | `{{date}}` |
+| Research Artifact | `{{research_artifact}}` |
+| Workspace | `{{workspace_name}}` |
+
+---
+
+## 1. Scope Confirmation
+
+**From Research Brief**:
+> [Quote the refined understanding from research]
+
+**Confirmed Inclusions**:
+- [What will be built]
+
+**Confirmed Exclusions**:
+- [What will NOT be built]
+
+---
+
+## 2. Objectives & Success Criteria
+
+### Primary Objectives
+1. [Objective 1]
+2. [Objective 2]
+
+### Success Criteria (from Research)
+| ID | Criteria | How to Verify |
+|----|----------|---------------|
+| SC-1 | [Measurable outcome] | [Verification method] |
+| SC-2 | [Measurable outcome] | [Verification method] |
+
+---
+
+## 3. Task Breakdown
+
+> **IMPORTANT**: The Executor MUST follow these tasks in order.
+> Each task should be completed and verified before moving to the next.
+
+| # | Task | Description | Acceptance Criteria | Effort | Dependencies |
+|---|------|-------------|---------------------|--------|--------------|
+| 1 | [Task Name] | [What to do] | [How to verify done] | S/M/L | None |
+| 2 | [Task Name] | [What to do] | [How to verify done] | S/M/L | Task 1 |
+| 3 | [Task Name] | [What to do] | [How to verify done] | S/M/L | Task 1, 2 |
+| 4 | [Task Name] | [What to do] | [How to verify done] | S/M/L | Task 3 |
+
+**Total Estimated Effort**: [Sum or range]
+
+### Task Details
+
+#### Task 1: [Task Name]
+- **Files to modify**: `path/to/file.ts`
+- **Implementation notes**: [Specific guidance for executor]
+- **Edge cases to handle**: [List any edge cases]
+
+#### Task 2: [Task Name]
+- **Files to modify**: `path/to/file.ts`
+- **Implementation notes**: [Specific guidance for executor]
+- **Edge cases to handle**: [List any edge cases]
+
+[Continue for each task...]
+
+---
+
+## 4. Validation Strategy
+
+> The Executor should run these validations after completing the relevant tasks.
+
+| Task(s) | Validation Type | Command / Steps |
+|---------|-----------------|-----------------|
+| 1-2 | Unit Tests | `npm test -- --grep 'feature'` |
+| 3 | Integration Test | `npm run test:integration` |
+| All | Type Check | `npm run typecheck` |
+| All | Lint | `npm run lint` |
+| All | Manual Verification | [Specific steps to manually verify] |
+
+### Manual Verification Checklist
+- [ ] [Step 1: What to check]
+- [ ] [Step 2: What to check]
+- [ ] [Step 3: What to check]
+
+---
+
+## 5. Risks & Mitigations
+
+| Risk | Impact | Likelihood | Mitigation | Owner |
+|------|--------|------------|------------|-------|
+| [Risk from research] | High/Med/Low | High/Med/Low | [How to mitigate] | Executor |
+| [Implementation risk] | High/Med/Low | High/Med/Low | [How to mitigate] | Executor |
+
+### Blockers Requiring Escalation
+- [Any known blockers that need external support]
+
+---
+
+## 6. Technical Guidance
+
+### Patterns to Follow
+From project-context.md and knowledge base:
+- [Pattern 1]: [Where to find example in codebase]
+- [Pattern 2]: [Where to find example in codebase]
+
+### Coding Conventions
+- [Convention 1 from project context]
+- [Convention 2 from project context]
+
+### Dependencies
+- [External dependency 1]: [How to use]
+- [Internal module 1]: [How to import/use]
+
+---
+
+## 7. Knowledge Updates
+
+Files to create/update in `{{CE_DATA}}/knowledge/` after implementation:
+
+| Action | File | Content |
+|--------|------|---------|
+| Create | `{{CE_DATA}}/knowledge/[domain].md` | [What to document] |
+| Update | `{{CE_DATA}}/knowledge/project-context.md` | [What changed] |
+
+---
+
+## 8. Handoff Checklist for Executor
+
+### Prerequisites Verified
+- [ ] Research brief exists and is complete
+- [ ] Project context is available
+- [ ] All dependencies are installed/available
+
+### Executor Must Have
+- [ ] Access to branch: `[branch name if specified]`
+- [ ] [Any required API keys, credentials, or access]
+- [ ] [Any required test data or fixtures]
+
+### During Execution
+- [ ] Follow tasks in order (1 → 2 → 3 → ...)
+- [ ] Run validation after each task
+- [ ] Document any deviations from this plan
+- [ ] Update meta.json status as you progress
+
+### After Execution
+- [ ] All tasks completed and verified
+- [ ] Execution log saved to `execution/{{task_slug}}-execution.md`
+- [ ] meta.json updated with final status
+
+---
+
+## 9. Open Questions (Carried Forward)
+
+From research phase (non-blocking):
+- [Question 1] - Can be resolved during execution
+- [Question 2] - Document resolution in execution log
+
+---
+
+> **Next Step**: `/execute TASK_SLUG={{task_slug}}`
+> 
+> Keep this plan under 500 lines. Remove unused rows or sections once populated.

package/agent-core/templates/research_output.md

@@ -0,0 +1,167 @@
+<!--
+  TEMPLATE: Research Brief
+  
+  HOW TO USE:
+  1. Copy to: {{CE_DATA}}/tasks/{{TASK_SLUG}}/research/{{TASK_SLUG}}-research.md
+  2. Replace {{variable}} placeholders with actual values
+  3. Delete sections that are empty after population
+  
+  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
+  - {{date}}: ISO date (YYYY-MM-DD)
+  - {{source}}: URL or reference to original request
+  - {{workspace_name}}: Project name
+  
+  NOTE: This document is the output of an interactive research session.
+  The Research agent engaged in constructive dialogue with the user to
+  achieve 100% understanding before this brief was generated.
+-->
+# Research Brief – {{task_title}}
+
+| Field | Value |
+|-------|-------|
+| Task ID | `{{task_id}}` |
+| Task Slug | `{{task_slug}}` |
+| Author | `{{author}}` |
+| Date | `{{date}}` |
+| Source Request | `{{source}}` |
+| Workspace | `{{workspace_name}}` |
+
+---
+
+## 1. Request Summary
+
+> **Original Request**: [Quote the user's initial request]
+
+**Refined Understanding** (after clarification):
+- [Clear, specific statement of what needs to be built]
+- [Why it needs to be built - problem/opportunity]
+
+---
+
+## 2. Clarification Summary
+
+The following was clarified through interactive dialogue:
+
+| Topic | Question Asked | User Response | Impact on Scope |
+|-------|----------------|---------------|-----------------|
+| Intent | | | |
+| Constraints | | | |
+| Success Criteria | | | |
+| Edge Cases | | | |
+
+**Key Decisions Made**:
+- [Decision 1 and rationale]
+- [Decision 2 and rationale]
+
+---
+
+## 3. Current Knowledge Snapshot
+
+Relevant prior work and context from project knowledge:
+
+| Source | Relevance |
+|--------|-----------|
+| `{{CE_DATA}}/knowledge/...` | [How it applies] |
+| [Search result] | [How it applies] |
+
+**Patterns to Follow**:
+- [Existing pattern 1 from codebase]
+- [Existing pattern 2 from codebase]
+
+---
+
+## 4. Requirements
+
+### Functional Requirements
+- [ ] [FR-1]: [Requirement description]
+- [ ] [FR-2]: [Requirement description]
+- [ ] [FR-3]: [Requirement description]
+
+### Non-Functional Requirements
+- [ ] [NFR-1]: [Performance/Security/etc. requirement]
+- [ ] [NFR-2]: [Requirement description]
+
+### Success Criteria
+How we'll know this is done:
+1. [Measurable outcome 1]
+2. [Measurable outcome 2]
+3. [Measurable outcome 3]
+
+---
+
+## 5. Scope Boundaries
+
+### In Scope
+- [Explicit inclusion 1]
+- [Explicit inclusion 2]
+
+### Out of Scope
+- [Explicit exclusion 1]
+- [Explicit exclusion 2]
+
+### Constraints
+- [Hard constraint 1 - e.g., timeline, tech, resources]
+- [Hard constraint 2]
+
+---
+
+## 6. Assumptions & Risks
+
+### Assumptions
+| ID | Assumption | Confidence | Validation Needed |
+|----|------------|------------|-------------------|
+| A1 | [Assumption] | High/Medium/Low | [How to validate] |
+| A2 | [Assumption] | High/Medium/Low | [How to validate] |
+
+### Risks
+| ID | Risk | Impact | Likelihood | Mitigation |
+|----|------|--------|------------|------------|
+| R1 | [Risk description] | High/Medium/Low | High/Medium/Low | [Mitigation] |
+| R2 | [Risk description] | High/Medium/Low | High/Medium/Low | [Mitigation] |
+
+---
+
+## 7. Opportunity & Alternative Approaches
+
+Approaches considered during research:
+
+| Approach | Pros | Cons | Recommendation |
+|----------|------|------|----------------|
+| [Approach A] | | | Chosen / Rejected |
+| [Approach B] | | | Chosen / Rejected |
+
+**Rationale for chosen approach**: [Explanation]
+
+---
+
+## 8. Hand-off Notes for Planning
+
+### Ready for Planning
+- [ ] Core requirements are clear and specific
+- [ ] Success criteria are measurable
+- [ ] Scope boundaries are explicit
+- [ ] No blocking open questions remain
+
+### Context for Planning Agent
+- [Important context the planner needs to know]
+- [Technical considerations for task breakdown]
+
+### Open Questions (Non-Blocking)
+- [Question that can be resolved during planning or execution]
+
+### References Added to meta.json
+- [List of knowledge files referenced]
+
+---
+
+> **Next Step**: `/plan TASK_SLUG={{task_slug}}`
+> 
+> Keep this document under 500 lines. Replace placeholders with concise entries and trim empty sections.

package/bin/ce-workflow.js

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+import '../dist/index.js';