orchestr8 2.1.4 → 2.2.0

package/.blueprint/agents/AGENT_SPECIFICATION_ALEX.md

@@ -117,8 +117,8 @@ Alex does not enforce breaking changes without explicit approval.
 
 ---
 
-## 📁 Use of `.blueprint/.business_context`
-Alex treats the `.blueprint/.business_context` directory as the **authoritative grounding** for:
+## 📁 Use of `.business_context`
+Alex treats the `.business_context` directory as the **authoritative grounding** for:
 - Domain context and constraints
 - Policy and legislative intent (where applicable)
 - Business outcomes and success measures
@@ -126,7 +126,7 @@ Alex treats the `.blueprint/.business_context` directory as the **authoritative
 
 Alex aligns system and feature specifications to this context.
 
-Because `.blueprint/.business_context` varies by project, Alex:
+Because `.business_context` varies by project, Alex:
 - Avoids over-assumption
 - Makes inferred interpretations explicit
 - Highlights where business context is ambiguous or incomplete

package/.blueprint/templates/SYSTEM_SPEC.md

@@ -14,7 +14,7 @@
 ---
 
 ## 2. Business & Domain Context
-**Grounded in `.blueprint/.business_context`.**
+**Grounded in `.business_context`.**
 
 - Relevant policy, legislation, or organisational drivers
 - Domain constraints the system must respect

package/.business_context/README.md

@@ -0,0 +1,27 @@
+# Business Context
+
+This directory contains business context documents that help the AI agents understand your domain, stakeholders, and existing systems.
+
+## What to include
+
+- **Domain glossary** - Key terms and definitions specific to your business
+- **Stakeholder information** - Who uses the system, their roles and needs
+- **Existing system documentation** - Architecture diagrams, API docs, data models
+- **Business rules** - Constraints, policies, and logic that govern the domain
+- **Compliance requirements** - Regulatory or legal considerations
+- **Integration points** - External systems and how they connect
+
+## How agents use this
+
+The agents (particularly Alex) reference these documents when:
+- Creating system specifications
+- Writing feature specifications
+- Ensuring consistency with domain language
+- Understanding constraints and dependencies
+
+## Tips
+
+- Keep documents concise and up-to-date
+- Use markdown for consistency
+- Link to external documentation rather than duplicating it
+- Update as your understanding of the domain evolves

package/README.md

@@ -29,7 +29,7 @@ This installs the `.blueprint/` directory and `SKILL.md` into your project. If f
 | `npx agent-workflow skills [agent]` | List recommended skills |
 | `npx agent-workflow help` | Show help |
 
-The `update` command preserves your content in `features/`, `system_specification/`, and `.business_context/` while updating the framework files.
+The `update` command preserves your content in `features/` and `system_specification/` while updating the framework files. Your `.business_context/` directory is separate from `.blueprint/` and unaffected by updates.
 
 ### Optional Skills
 
@@ -71,19 +71,22 @@ Update System:  Alex → cascade check
 ## Directory Structure
 
 ```
-.blueprint/
-├── agents/                    # Agent specifications
-│   ├── AGENT_SPECIFICATION_ALEX.md
-│   ├── AGENT_BA_CASS.md
-│   ├── AGENT_TESTER_NIGEL.md
-│   └── AGENT_DEVELOPER_CODEY.md
-├── templates/                 # Spec templates
-│   ├── SYSTEM_SPEC.md
-│   └── FEATURE_SPEC.md
-├── ways_of_working/           # Development rituals
-├── features/                  # Feature specs (created per feature)
-├── system_specification/      # System spec (created on first run)
-└── .business_context/         # Project-specific context
+your-project/
+├── .blueprint/
+│   ├── agents/                    # Agent specifications
+│   │   ├── AGENT_SPECIFICATION_ALEX.md
+│   │   ├── AGENT_BA_CASS.md
+│   │   ├── AGENT_TESTER_NIGEL.md
+│   │   └── AGENT_DEVELOPER_CODEY.md
+│   ├── templates/                 # Spec templates
+│   │   ├── SYSTEM_SPEC.md
+│   │   └── FEATURE_SPEC.md
+│   ├── ways_of_working/           # Development rituals
+│   ├── features/                  # Feature specs (created per feature)
+│   └── system_specification/      # System spec (created on first run)
+├── .business_context/             # Business context documents
+│   └── README.md
+└── SKILL.md
 ```
 
 ## How It Works

package/SKILL.md

@@ -82,7 +82,7 @@ Create a feature specification for "{slug}".
 ## Inputs (read these files)
 - System Spec: .blueprint/system_specification/SYSTEM_SPEC.md
 - Template: .blueprint/templates/FEATURE_SPEC.md
-- Business Context: .blueprint/.business_context/
+- Business Context: .business_context/
 
 ## Output (write this file)
 Write the feature spec to: {FEAT_DIR}/FEATURE_SPEC.md

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "orchestr8",
-  "version": "2.1.4",
+  "version": "2.2.0",
   "description": "Multi-agent workflow framework for automated feature development",
   "main": "src/index.js",
   "bin": {
@@ -30,6 +30,7 @@
     "bin",
     "src",
     ".blueprint",
+    ".business_context",
     "SKILL.md"
   ]
 }

package/src/init.js

@@ -60,6 +60,8 @@ function updateGitignore() {
 async function init() {
   const blueprintSrc = path.join(PACKAGE_ROOT, '.blueprint');
   const blueprintDest = path.join(TARGET_DIR, '.blueprint');
+  const businessContextSrc = path.join(PACKAGE_ROOT, '.business_context');
+  const businessContextDest = path.join(TARGET_DIR, '.business_context');
   const skillSrc = path.join(PACKAGE_ROOT, 'SKILL.md');
   const skillDest = path.join(TARGET_DIR, 'SKILL.md');
 
@@ -92,6 +94,15 @@ async function init() {
   copyDir(blueprintSrc, blueprintDest);
   console.log('Copied .blueprint directory');
 
+  // Copy .business_context directory
+  if (!fs.existsSync(businessContextDest)) {
+    console.log('Copying .business_context directory...');
+    copyDir(businessContextSrc, businessContextDest);
+    console.log('Copied .business_context directory');
+  } else {
+    console.log('.business_context directory already exists, skipping');
+  }
+
   // Update .gitignore
   updateGitignore();
 
@@ -99,7 +110,7 @@ async function init() {
 agent-workflow initialized successfully!
 
 Next steps:
-1. Add business context to .blueprint/.business_context/
+1. Add business context documents to .business_context/
 2. Run /implement-feature in Claude Code to start your first feature
 `);
 }

package/src/update.js

@@ -8,8 +8,7 @@ const TARGET_DIR = process.cwd();
 // Directories that contain user content and should NOT be overwritten
 const USER_CONTENT_DIRS = [
   'features',
-  'system_specification',
-  '.business_context'
+  'system_specification'
 ];
 
 // Directories/files that should be updated
@@ -63,7 +62,7 @@ async function update() {
   }
 
   console.log('Updating agent-workflow...');
-  console.log('(Preserving: features/, system_specification/, .business_context/)\n');
+  console.log('(Preserving: features/, system_specification/)\n');
 
   // Update each updatable directory
   for (const dir of UPDATABLE) {
@@ -98,7 +97,7 @@ Updated:
 Preserved:
   - .blueprint/features/
   - .blueprint/system_specification/
-  - .blueprint/.business_context/
+  - .business_context/
 `);
 }