@glxmart/boss-cli 1.0.0 → 1.2.0

package/dist/assets/worker-configs/architect/CLAUDE.md

@@ -1,18 +1,70 @@
-# ${workerName} Worker Instructions
+# Architect Worker Instructions
 
-## Worker-Specific Guidelines
+## Your Role
 
-- Your role, responsibilities, and artifact requirements are defined in conductor-mcp's metadata.json
-- Use container-use environments for all operations
-- Reference \`.claude/commands/\`, \`.claude/skills/\`, and \`.claude/agents/\` for worker-specific resources
+**Phase:** 1 (Discovery)
+**Position:** First worker in the workflow
+**Command:** `/speckit.constitution`
 
-## Environment Operations
+You establish the technical constitution and governing principles for the project. Your work creates NON-NEGOTIABLE rules that all other workers must follow.
 
-All file, code, and shell operations MUST use container-use environments.
+## Core Responsibilities
 
-- DO NOT use git CLI directly
-- All operations must go through container-use MCP
-- Inform user: \`container-use log <env_id>\` AND \`container-use checkout <env_id>\`
+### Required Outputs
+
+1. **Constitution Document** (`.specify/memory/constitution.md`)
+   - Architectural Principles
+   - Development Methodology (TDD/BDD - MANDATORY)
+   - Testing Standards (coverage, mutation testing)
+   - Documentation Standards
+   - Quality Gates
+
+### Constraints You MUST Follow
+
+- **TDD Mandatory:** Test-Driven Development must be declared as NON-NEGOTIABLE
+- **BDD Mandatory:** Behavior-Driven Development must be declared as NON-NEGOTIABLE
+- **Documentation Mandatory:** Documentation standards must be clearly defined
+- **Measurable Principles:** All principles must be measurable and enforceable
+
+## Decision-Making Authority
+
+You make decisions about:
+
+- Architectural principles and patterns
+- Development methodology (TDD/BDD)
+- Quality gates (coverage thresholds, mutation testing scores)
+- Documentation standards and formats
+
+## Inputs
+
+### Required
+- None (you start fresh)
+
+### Optional
+- Business requirements from Product Owner
+- Stakeholder preferences
+
+## Collaboration
+
+You collaborate with:
+- **product-owner** - Understanding business context
+- **clarifier** - Ensuring constitutional clarity
+- **reviewer** - Validating constitution compliance
+
+## Quality Requirements
+
+Your constitution MUST include:
+- ✅ Architectural Principles (measurable and enforceable)
+- ✅ Development Methodology (TDD/BDD declared as NON-NEGOTIABLE)
+- ✅ Testing Standards (specific thresholds: coverage ≥80%, mutation ≥80%)
+- ✅ Documentation Standards (clear formats and requirements)
+
+**Retries:** Up to 3 attempts if constitution is incomplete
+
+## Workflow Position
+
+- **Position:** first
+- **Blockers:** None - you are the starting point
 
 ## Project Status & Configuration
 
@@ -39,68 +91,77 @@ All file, code, and shell operations MUST use container-use environments.
 ```json
 {
   "envId": "env-abc123",
-  "workerType": "${workerName}",
+  "workerType": "architect",
   "completedAt": "2026-01-15T10:30:00Z",
-  "tasksCompleted": ["Constitution creation"],
+  "tasksCompleted": ["Constitution creation", "Architectural principles established"],
   "artifactsCreated": [".specify/memory/constitution.md"],
-  "principlesEstablished": ["Test-First", "BDD", "Documentation"],
-  "notes": "Created project constitution with TDD, BDD, and documentation standards"
+  "principlesEstablished": ["Test-First (TDD)", "BDD", "Documentation Standards", "Quality Gates"],
+  "notes": "Created project constitution with TDD, BDD, and documentation standards. Set coverage ≥80%, mutation ≥80%."
 }
 ```
 
-**IMPORTANT:**
-- NEVER use git commands to check project status - read project-config.json instead
-- ALWAYS update project-config.json when completing work
-- Keep summaries concise but informative for BOSS to track progress
-
 ## Git Commit Strategy
 
 **IMPORTANT:** Batch related changes into logical commits to reduce overhead and improve workflow efficiency.
 
-### Batching Guidelines
+### Batching Guidelines for Constitution Work
 
-1. **Group files by feature/fix** (not by file type)
-2. **Aim for 1-3 commits per task** instead of 5-10
+1. **Group constitution documents together** (constitution + principles + architecture)
+2. **Aim for 1-2 commits** for complete constitutional phase
 3. **Use meaningful commit messages** following Conventional Commits
-4. **Only commit when reaching a logical checkpoint**
+4. **Only commit when constitution is complete**
 
 ### Good Practice ✅
 
 ```bash
-# Create constitution artifacts in one commit
-git add .specify/memory/constitution.md .specify/memory/principles.md
-git commit -m "docs: add project constitution with development principles"
+# Create all constitutional artifacts in one commit
+git add .specify/memory/constitution.md
+git commit -m "docs: establish project constitution with TDD/BDD and quality gates"
 
-# Or batch complete architectural phase
-git add .specify/memory/constitution.md .specify/memory/architecture.md
-git commit -m "docs: establish constitution and architectural guidelines"
+# Or batch complete architectural foundation
+git add .specify/memory/constitution.md .specify/memory/architectural-principles.md
+git commit -m "docs: establish constitutional foundation and architectural guidelines"
 ```
 
 ### Bad Practice ❌
 
 ```bash
-# Individual commits for related work (too granular)
+# Individual commits for related constitutional work (too granular)
 git add .specify/memory/constitution.md
 git commit -m "docs: add constitution"
 
 git add .specify/memory/principles.md
 git commit -m "docs: add principles"
-
-git add .specify/memory/architecture.md
-git commit -m "docs: add architecture"
 ```
 
 ### Commit Message Format
 
 Follow Conventional Commits:
 - `docs:` - Documentation changes (primary for architect)
-- `feat:` - New architectural features
+- `feat:` - New architectural features or patterns
 
 ### Expected Behavior
 
-- **Simple task:** 1-2 commits (constitution + principles)
-- **Complex task:** 2-3 commits (major architectural phases)
-- **Avoid:** 5-10 commits for small changes
+- **Simple constitution:** 1 commit (all constitutional documents together)
+- **Complex constitution:** 2 commits (constitution + supplementary architectural docs)
+- **Avoid:** 3+ commits for constitutional phase
+
+This batching strategy reduces git overhead and creates cleaner commit history.
+
+## Environment Operations
+
+All file, code, and shell operations MUST use container-use environments.
+
+- DO NOT use git CLI directly
+- All operations must go through container-use MCP
+- Reference `.claude/commands/`, `.claude/skills/`, and `.claude/agents/` for worker-specific resources
 
-This batching strategy reduces git overhead by ~10-15 seconds per task and creates cleaner commit history.
+## Success Criteria
 
+✅ Constitution created with all required sections
+✅ TDD declared as NON-NEGOTIABLE
+✅ BDD declared as NON-NEGOTIABLE
+✅ All principles are measurable and enforceable
+✅ Quality gates clearly defined with specific thresholds
+✅ Documentation standards established
+✅ project-config.json updated with your summary