@glxmart/boss-cli 1.0.0-beta.0

package/dist/assets/worker-configs/code-reviewer/CLAUDE.md

@@ -0,0 +1,113 @@
+# ${workerName} Worker Instructions
+
+This worker is responsible for ${workerRoleDescription}
+
+## Worker-Specific Guidelines
+
+- Follow the prompt in \`prompt.md\` for detailed role instructions
+- Use container-use environments for all operations
+- Reference \`.claude/commands/\`, \`.claude/skills/\`, and \`.claude/agents/\` for worker-specific resources
+
+## 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
+- Inform user: \`container-use log <env_id>\` AND \`container-use checkout <env_id>\`
+
+## Project Status & Configuration
+
+**CRITICAL:** Always check `.boss/project-config.json` to understand project state before starting work.
+
+**Read project-config.json to understand:**
+- Current branch and workflow stage
+- Active workers and their status
+- Completed tasks
+- Repository information
+- Initialization status
+
+**Update project-config.json when:**
+- Starting work: Add your environment ID to `workflow.activeWorkers`
+- Completing work: Add a summary to `workers.summaries` with:
+  - Environment ID
+  - Tasks completed
+  - Artifacts created (review reports, feedback)
+  - Code quality metrics
+  - Issues found and resolved
+  - Any blockers or issues encountered
+- After merging: Remove from `workflow.activeWorkers` and add to `workflow.completedTasks`
+
+**Example worker summary format:**
+```json
+{
+  "envId": "env-abc123",
+  "workerType": "${workerName}",
+  "completedAt": "2026-01-15T10:30:00Z",
+  "tasksCompleted": ["Code review", "Test review", "Quality validation"],
+  "artifactsCreated": ["review-report.md"],
+  "issuesFound": 3,
+  "issuesResolved": 3,
+  "approvalStatus": "approved",
+  "notes": "Completed code review with 3 minor issues resolved"
+}
+```
+
+**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
+
+1. **Group files by feature/fix** (not by file type)
+2. **Aim for 1-3 commits per task** instead of 5-10
+3. **Use meaningful commit messages** following Conventional Commits
+4. **Only commit when reaching a logical checkpoint**
+
+### Good Practice ✅
+
+```bash
+# Create review artifacts in one commit
+git add review-report.md review-feedback.json
+git commit -m "docs: add code review report with feedback"
+
+# Or batch review fixes
+git add src/api/users.ts tests/api/users.test.ts
+git commit -m "fix: address code review feedback - add error handling and tests"
+```
+
+### Bad Practice ❌
+
+```bash
+# Individual commits for related work (too granular)
+git add review-report.md
+git commit -m "docs: add report"
+
+git add review-feedback.json
+git commit -m "docs: add feedback"
+
+git add src/api/users.ts
+git commit -m "fix: fix issue 1"
+```
+
+### Commit Message Format
+
+Follow Conventional Commits:
+- `docs:` - Documentation changes (review reports)
+- `fix:` - Bug fixes based on review
+- `refactor:` - Code improvements from review
+- `style:` - Code style fixes
+
+### Expected Behavior
+
+- **Simple task:** 1-2 commits (review report + fixes)
+- **Complex task:** 2-3 commits (review phases)
+- **Avoid:** 5-10 commits for small changes
+
+This batching strategy reduces git overhead by ~10-15 seconds per task and creates cleaner commit history.
+

package/dist/assets/worker-configs/consolidator/.claude/commands/.gitkeep

@@ -0,0 +1 @@
+

package/dist/assets/worker-configs/consolidator/.claude/skills/.gitkeep

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,114 @@
+# ${workerName} Worker Instructions
+
+This worker is responsible for ${workerRoleDescription}
+
+## Worker-Specific Guidelines
+
+- Follow the prompt in \`prompt.md\` for detailed role instructions
+- Use container-use environments for all operations
+- Reference \`.claude/commands/\`, \`.claude/skills/\`, and \`.claude/agents/\` for worker-specific resources
+
+## 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
+- Inform user: \`container-use log <env_id>\` AND \`container-use checkout <env_id>\`
+
+## Project Status & Configuration
+
+**CRITICAL:** Always check `.boss/project-config.json` to understand project state before starting work.
+
+**Read project-config.json to understand:**
+- Current branch and workflow stage
+- Active workers and their status
+- Completed tasks
+- Repository information
+- Initialization status
+- Worker summaries from previous phases
+
+**Update project-config.json when:**
+- Starting work: Add your environment ID to `workflow.activeWorkers`
+- Completing work: Add a summary to `workers.summaries` with:
+  - Environment ID
+  - Tasks completed
+  - Artifacts created (quickstart.md, checklist.md)
+  - Branches merged
+  - Documentation consolidated
+  - Any blockers or issues encountered
+- After merging: Remove from `workflow.activeWorkers` and add to `workflow.completedTasks`
+- Update `workflow.stage` to reflect completion
+
+**Example worker summary format:**
+```json
+{
+  "envId": "env-abc123",
+  "workerType": "${workerName}",
+  "completedAt": "2026-01-15T10:30:00Z",
+  "tasksCompleted": ["Consolidation phase"],
+  "artifactsCreated": [".specify/specs/001-feature/quickstart.md", ".specify/specs/001-feature/checklist.md"],
+  "branchesMerged": 5,
+  "documentationConsolidated": true,
+  "notes": "Merged all worker branches and created delivery artifacts"
+}
+```
+
+**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
+- Review all worker summaries from previous phases to understand what was completed
+
+## Git Commit Strategy
+
+**IMPORTANT:** Batch related changes into logical commits to reduce overhead and improve workflow efficiency.
+
+### Batching Guidelines
+
+1. **Group files by feature/fix** (not by file type)
+2. **Aim for 1-3 commits per task** instead of 5-10
+3. **Use meaningful commit messages** following Conventional Commits
+4. **Only commit when reaching a logical checkpoint**
+
+### Good Practice ✅
+
+```bash
+# Create consolidation artifacts in one commit
+git add .specify/specs/001-feature/quickstart.md .specify/specs/001-feature/checklist.md
+git commit -m "docs: add delivery artifacts - quickstart and checklist"
+
+# Or batch branch merges and documentation
+git add .specify/specs/001-feature/quickstart.md README.md CHANGELOG.md
+git commit -m "docs: consolidate documentation and create delivery artifacts"
+```
+
+### Bad Practice ❌
+
+```bash
+# Individual commits for related work (too granular)
+git add .specify/specs/001-feature/quickstart.md
+git commit -m "docs: add quickstart"
+
+git add .specify/specs/001-feature/checklist.md
+git commit -m "docs: add checklist"
+
+git add README.md
+git commit -m "docs: update README"
+```
+
+### Commit Message Format
+
+Follow Conventional Commits:
+- `docs:` - Documentation changes (primary for consolidator)
+- `chore:` - Maintenance tasks (branch merges, cleanup)
+- `feat:` - New feature consolidation
+
+### Expected Behavior
+
+- **Simple task:** 1-2 commits (consolidation + finalization)
+- **Complex task:** 2-3 commits (major consolidation phases)
+- **Avoid:** 5-10 commits for small changes
+
+This batching strategy reduces git overhead by ~10-15 seconds per task and creates cleaner commit history.
+

package/dist/assets/worker-configs/developer-backend/.claude/commands/.gitkeep

@@ -0,0 +1 @@
+

package/dist/assets/worker-configs/developer-backend/.claude/skills/.gitkeep

@@ -0,0 +1 @@
+

package/dist/assets/worker-configs/developer-backend/CLAUDE.md

@@ -0,0 +1,116 @@
+# ${workerName} Worker Instructions
+
+This worker is responsible for ${workerRoleDescription}
+
+## Worker-Specific Guidelines
+
+- Follow the prompt in \`prompt.md\` for detailed role instructions
+- Use container-use environments for all operations
+- Reference \`.claude/commands/\`, \`.claude/skills/\`, and \`.claude/agents/\` for worker-specific resources
+
+## 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
+- Inform user: \`container-use log <env_id>\` AND \`container-use checkout <env_id>\`
+
+## Project Status & Configuration
+
+**CRITICAL:** Always check `.boss/project-config.json` to understand project state before starting work.
+
+**Read project-config.json to understand:**
+- Current branch and workflow stage
+- Active workers and their status
+- Completed tasks
+- Repository information
+- Initialization status
+
+**Update project-config.json when:**
+- Starting work: Add your environment ID to `workflow.activeWorkers`
+- Completing work: Add a summary to `workers.summaries` with:
+  - Environment ID
+  - Tasks completed
+  - Files changed
+  - Tests written/updated
+  - Documentation created
+  - Any blockers or issues encountered
+- After merging: Remove from `workflow.activeWorkers` and add to `workflow.completedTasks`
+
+**Example worker summary format:**
+```json
+{
+  "envId": "env-abc123",
+  "workerType": "${workerName}",
+  "completedAt": "2026-01-15T10:30:00Z",
+  "tasksCompleted": ["T010", "T011", "T012"],
+  "filesChanged": ["src/api/users.ts", "tests/api/users.test.ts"],
+  "testsWritten": 5,
+  "testsUpdated": 2,
+  "documentationCreated": ["docs/api/users.md"],
+  "notes": "Implemented user authentication endpoints with TDD"
+}
+```
+
+**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
+
+1. **Group files by feature/fix** (not by file type)
+2. **Aim for 1-3 commits per task** instead of 5-10
+3. **Use meaningful commit messages** following Conventional Commits
+4. **Only commit when reaching a logical checkpoint**
+
+### Good Practice ✅
+
+```bash
+# Create multiple related files in one commit
+git add src/api/users.ts src/middleware/auth.ts tests/api/users.test.ts
+git commit -m "feat: add user API with authentication middleware and tests"
+
+# Or batch a complete backend feature
+git add src/database/models/User.ts src/services/UserService.ts tests/services/UserService.test.ts
+git commit -m "feat: implement user service with database model and test coverage"
+```
+
+### Bad Practice ❌
+
+```bash
+# Individual commits for related work (too granular)
+git add src/api/users.ts
+git commit -m "feat: add API"
+
+git add src/middleware/auth.ts
+git commit -m "feat: add middleware"
+
+git add tests/api/users.test.ts
+git commit -m "test: add tests"
+```
+
+### Commit Message Format
+
+Follow Conventional Commits:
+- `feat:` - New feature
+- `fix:` - Bug fix
+- `refactor:` - Code refactoring
+- `test:` - Adding/updating tests
+- `docs:` - Documentation changes
+- `style:` - Code style changes (formatting, etc.)
+- `perf:` - Performance improvements
+
+### Expected Behavior
+
+- **Simple task:** 1-2 commits (setup + implementation)
+- **Complex task:** 2-3 commits (major logical phases)
+- **Avoid:** 5-10 commits for small changes
+
+This batching strategy reduces git overhead by ~10-15 seconds per task and creates cleaner commit history.
+

package/dist/assets/worker-configs/developer-frontend/.claude/commands/.gitkeep

@@ -0,0 +1 @@
+

package/dist/assets/worker-configs/developer-frontend/.claude/skills/.gitkeep

@@ -0,0 +1 @@
+

package/dist/assets/worker-configs/developer-frontend/CLAUDE.md

@@ -0,0 +1,116 @@
+# ${workerName} Worker Instructions
+
+This worker is responsible for ${workerRoleDescription}
+
+## Worker-Specific Guidelines
+
+- Follow the prompt in \`prompt.md\` for detailed role instructions
+- Use container-use environments for all operations
+- Reference \`.claude/commands/\`, \`.claude/skills/\`, and \`.claude/agents/\` for worker-specific resources
+
+## 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
+- Inform user: \`container-use log <env_id>\` AND \`container-use checkout <env_id>\`
+
+## Project Status & Configuration
+
+**CRITICAL:** Always check `.boss/project-config.json` to understand project state before starting work.
+
+**Read project-config.json to understand:**
+- Current branch and workflow stage
+- Active workers and their status
+- Completed tasks
+- Repository information
+- Initialization status
+
+**Update project-config.json when:**
+- Starting work: Add your environment ID to `workflow.activeWorkers`
+- Completing work: Add a summary to `workers.summaries` with:
+  - Environment ID
+  - Tasks completed
+  - Files changed
+  - Tests written/updated
+  - Documentation created
+  - Any blockers or issues encountered
+- After merging: Remove from `workflow.activeWorkers` and add to `workflow.completedTasks`
+
+**Example worker summary format:**
+```json
+{
+  "envId": "env-abc123",
+  "workerType": "${workerName}",
+  "completedAt": "2026-01-15T10:30:00Z",
+  "tasksCompleted": ["T010", "T011", "T012"],
+  "filesChanged": ["src/components/UserCard.tsx", "tests/components/UserCard.test.tsx"],
+  "testsWritten": 5,
+  "testsUpdated": 2,
+  "documentationCreated": ["docs/components/UserCard.md"],
+  "notes": "Implemented UserCard component with TDD and Storybook"
+}
+```
+
+**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
+
+1. **Group files by feature/fix** (not by file type)
+2. **Aim for 1-3 commits per task** instead of 5-10
+3. **Use meaningful commit messages** following Conventional Commits
+4. **Only commit when reaching a logical checkpoint**
+
+### Good Practice ✅
+
+```bash
+# Create multiple related files in one commit
+git add src/components/Button.tsx src/components/Button.test.tsx src/styles/Button.css
+git commit -m "feat: add button component with styles and tests"
+
+# Or batch a complete frontend feature
+git add src/pages/Dashboard.tsx src/hooks/useDashboard.ts tests/pages/Dashboard.test.tsx
+git commit -m "feat: implement dashboard page with custom hook and test coverage"
+```
+
+### Bad Practice ❌
+
+```bash
+# Individual commits for related work (too granular)
+git add src/components/Button.tsx
+git commit -m "feat: add component"
+
+git add src/styles/Button.css
+git commit -m "style: add styles"
+
+git add src/components/Button.test.tsx
+git commit -m "test: add tests"
+```
+
+### Commit Message Format
+
+Follow Conventional Commits:
+- `feat:` - New feature
+- `fix:` - Bug fix
+- `refactor:` - Code refactoring
+- `test:` - Adding/updating tests
+- `docs:` - Documentation changes
+- `style:` - Code style changes (formatting, etc.)
+- `perf:` - Performance improvements
+
+### Expected Behavior
+
+- **Simple task:** 1-2 commits (setup + implementation)
+- **Complex task:** 2-3 commits (major logical phases)
+- **Avoid:** 5-10 commits for small changes
+
+This batching strategy reduces git overhead by ~10-15 seconds per task and creates cleaner commit history.
+

package/dist/assets/worker-configs/developer-fullstack/.claude/commands/.gitkeep

@@ -0,0 +1 @@
+

package/dist/assets/worker-configs/developer-fullstack/.claude/skills/.gitkeep

@@ -0,0 +1 @@
+

package/dist/assets/worker-configs/developer-fullstack/CLAUDE.md

@@ -0,0 +1,116 @@
+# ${workerName} Worker Instructions
+
+This worker is responsible for ${workerRoleDescription}
+
+## Worker-Specific Guidelines
+
+- Follow the prompt in \`prompt.md\` for detailed role instructions
+- Use container-use environments for all operations
+- Reference \`.claude/commands/\`, \`.claude/skills/\`, and \`.claude/agents/\` for worker-specific resources
+
+## 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
+- Inform user: \`container-use log <env_id>\` AND \`container-use checkout <env_id>\`
+
+## Project Status & Configuration
+
+**CRITICAL:** Always check `.boss/project-config.json` to understand project state before starting work.
+
+**Read project-config.json to understand:**
+- Current branch and workflow stage
+- Active workers and their status
+- Completed tasks
+- Repository information
+- Initialization status
+
+**Update project-config.json when:**
+- Starting work: Add your environment ID to `workflow.activeWorkers`
+- Completing work: Add a summary to `workers.summaries` with:
+  - Environment ID
+  - Tasks completed
+  - Files changed
+  - Tests written/updated
+  - Documentation created
+  - Any blockers or issues encountered
+- After merging: Remove from `workflow.activeWorkers` and add to `workflow.completedTasks`
+
+**Example worker summary format:**
+```json
+{
+  "envId": "env-abc123",
+  "workerType": "${workerName}",
+  "completedAt": "2026-01-15T10:30:00Z",
+  "tasksCompleted": ["T010", "T011", "T012"],
+  "filesChanged": ["src/api/users.ts", "src/components/UserCard.tsx", "tests/api/users.test.ts"],
+  "testsWritten": 8,
+  "testsUpdated": 3,
+  "documentationCreated": ["docs/api/users.md", "docs/components/UserCard.md"],
+  "notes": "Implemented fullstack user authentication with TDD"
+}
+```
+
+**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
+
+1. **Group files by feature/fix** (not by file type)
+2. **Aim for 1-3 commits per task** instead of 5-10
+3. **Use meaningful commit messages** following Conventional Commits
+4. **Only commit when reaching a logical checkpoint**
+
+### Good Practice ✅
+
+```bash
+# Create multiple related files in one commit
+git add src/components/UserProfile.tsx src/components/UserProfile.test.tsx
+git commit -m "feat: add user profile component with tests"
+
+# Or batch a complete feature implementation
+git add src/api/auth.ts src/hooks/useAuth.ts tests/api/auth.test.ts
+git commit -m "feat: implement authentication API and hooks with test coverage"
+```
+
+### Bad Practice ❌
+
+```bash
+# Individual commits for related work (too granular)
+git add src/components/UserProfile.tsx
+git commit -m "feat: add component"
+
+git add src/components/UserProfile.test.tsx
+git commit -m "test: add component tests"
+
+git add src/styles/UserProfile.css
+git commit -m "style: add component styles"
+```
+
+### Commit Message Format
+
+Follow Conventional Commits:
+- `feat:` - New feature
+- `fix:` - Bug fix
+- `refactor:` - Code refactoring
+- `test:` - Adding/updating tests
+- `docs:` - Documentation changes
+- `style:` - Code style changes (formatting, etc.)
+- `perf:` - Performance improvements
+
+### Expected Behavior
+
+- **Simple task:** 1-2 commits (setup + implementation)
+- **Complex task:** 2-3 commits (major logical phases)
+- **Avoid:** 5-10 commits for small changes
+
+This batching strategy reduces git overhead by ~10-15 seconds per task and creates cleaner commit history.
+