@glxmart/boss-cli 1.0.0-beta.0

package/dist/assets/template-docs/nextjs-app-turbo.md

@@ -0,0 +1,102 @@
+# Template Documentation: Next.js App (Turbo)
+
+This project was bootstrapped using the **Next.js App (Turbo)** template, which provides a modern full-stack web application setup.
+
+## What Was Included
+
+### Core Stack
+- **Next.js 15** - React framework with App Router
+- **React 18** - UI library
+- **TypeScript** - Type-safe development
+- **Tailwind CSS** - Utility-first CSS (via T3 template)
+- **Prisma** - Database ORM (via T3 template)
+- **Vitest** - Testing framework
+- **ESLint** - Code linting with React support (ESLint 9 flat config)
+- **Prettier** - Code formatting
+
+### Project Structure
+
+\`\`\`
+${config.name}/
+├── src/
+│   └── app/                # Next.js App Router pages
+├── public/                 # Static assets
+├── tests/                  # Test files
+├── docs/                   # Documentation
+├── .boss/                  # BOSS configuration
+├── .specify/               # Spec-Kit structure
+├── .container-use/         # Container-use config
+├── .claude/                # Claude Code rules
+├── .github/                # GitHub workflows
+├── .husky/                 # Git hooks
+├── scripts/                # Utility scripts
+├── package.json            # Dependencies and scripts
+├── tsconfig.json           # TypeScript configuration
+├── next.config.js          # Next.js configuration
+├── vitest.config.ts        # Test configuration
+├── eslint.config.js        # ESLint configuration (ESLint 9)
+└── docker-compose.yml      # Local infrastructure
+\`\`\`
+
+### Available Scripts
+
+- \`pnpm dev\` - Start development server
+- \`pnpm build\` - Build for production
+- \`pnpm start\` - Start production server
+- \`pnpm typecheck\` - Type check without emitting files
+- \`pnpm lint\` - Lint code with ESLint
+- \`pnpm test\` - Run tests in watch mode
+- \`pnpm test:unit\` - Run unit tests (excludes e2e/integration)
+- \`pnpm test:coverage\` - Run tests with coverage
+
+### Features
+
+- **App Router** - Next.js 15 App Router for modern routing
+- **Server Components** - React Server Components by default
+- **Type Safety** - Full TypeScript support throughout
+- **Fast Refresh** - Instant feedback during development
+- **Optimized Builds** - Production-ready optimizations
+
+### Quality Preset: ${config.quality}
+
+This project uses the **${config.quality}** quality preset, which defines:
+- Code coverage thresholds
+- Quality gate requirements
+- Testing requirements
+- Linting and type checking rules
+
+### Git Hooks
+
+The following git hooks are configured:
+
+- **pre-commit** - Runs lint-staged (ESLint + Prettier) and tests for changed files
+- **commit-msg** - Validates commit messages follow Conventional Commits v1.0.0
+- **pre-push** - Runs comprehensive validation (typecheck, lint, tests, security checks)
+
+### Next Steps
+
+1. **Start Development**
+   \`\`\`bash
+   pnpm install
+   pnpm dev
+   \`\`\`
+
+2. **Add Pages**
+   - Create pages in \`src/app/\` directory
+   - Use Server Components by default
+   - Add Client Components when needed with \`"use client"\`
+
+3. **Add Styling**
+   - Use Tailwind CSS classes
+   - Configure in \`tailwind.config.js\`
+
+4. **Use BOSS**
+   - Run \`./start-boss.sh\` to start BOSS orchestration
+   - BOSS will help you build features following the Spec-Kit workflow
+
+### Documentation
+
+- [Next.js Documentation](https://nextjs.org/docs)
+- [React Documentation](https://react.dev)
+- [TypeScript Documentation](https://www.typescriptlang.org/docs)
+

package/dist/assets/template-docs/t3-app.md

@@ -0,0 +1,106 @@
+# Template Documentation: T3 Stack
+
+This project was bootstrapped using the **T3 Stack** template, which provides a full-stack TypeScript application with best practices.
+
+## What Was Included
+
+### Core Stack
+- **Next.js** - React framework with App Router
+- **TypeScript** - Type-safe development
+- **Tailwind CSS** - Utility-first CSS
+- **tRPC** - End-to-end typesafe APIs
+- **Prisma** - Next-generation ORM
+- **NextAuth.js** - Authentication
+- **Vitest** - Testing framework
+- **ESLint** - Code linting (ESLint 9 flat config)
+- **Prettier** - Code formatting
+
+### Project Structure
+
+\`\`\`
+${config.name}/
+├── src/
+│   ├── app/                # Next.js App Router pages
+│   ├── server/             # Server-side code (tRPC, Prisma)
+│   └── components/         # React components
+├── public/                 # Static assets
+├── prisma/                 # Prisma schema and migrations
+├── tests/                  # Test files
+├── docs/                   # Documentation
+├── .boss/                  # BOSS configuration
+├── .specify/               # Spec-Kit structure
+├── .container-use/         # Container-use config
+├── .claude/                # Claude Code rules
+├── .github/                # GitHub workflows
+├── .husky/                 # Git hooks
+├── scripts/                # Utility scripts
+├── package.json            # Dependencies and scripts
+└── docker-compose.yml      # Local infrastructure
+\`\`\`
+
+### Available Scripts
+
+- \`pnpm dev\` - Start development server
+- \`pnpm build\` - Build for production
+- \`pnpm start\` - Start production server
+- \`pnpm typecheck\` - Type check without emitting files
+- \`pnpm lint\` - Lint code with ESLint
+- \`pnpm test\` - Run tests in watch mode
+- \`pnpm test:unit\` - Run unit tests (excludes e2e/integration)
+- \`pnpm test:coverage\` - Run tests with coverage
+- \`pnpm db:push\` - Push Prisma schema to database
+- \`pnpm db:studio\` - Open Prisma Studio
+
+### Features
+
+- **End-to-End Type Safety** - tRPC provides type-safe APIs from server to client
+- **Database ORM** - Prisma for type-safe database access
+- **Authentication** - NextAuth.js for secure authentication
+- **Styling** - Tailwind CSS for utility-first styling
+- **Full-Stack** - Server and client code in one TypeScript project
+
+### Quality Preset: ${config.quality}
+
+This project uses the **${config.quality}** quality preset, which defines:
+- Code coverage thresholds
+- Quality gate requirements
+- Testing requirements
+- Linting and type checking rules
+
+### Git Hooks
+
+The following git hooks are configured:
+
+- **pre-commit** - Runs lint-staged (ESLint + Prettier) and tests for changed files
+- **commit-msg** - Validates commit messages follow Conventional Commits v1.0.0
+- **pre-push** - Runs comprehensive validation (typecheck, lint, tests, security checks)
+
+### Next Steps
+
+1. **Start Development**
+   \`\`\`bash
+   pnpm install
+   pnpm db:push
+   pnpm dev
+   \`\`\`
+
+2. **Configure Database**
+   - Update \`prisma/schema.prisma\` with your database schema
+   - Run \`pnpm db:push\` to sync schema
+   - Use Prisma Client in your server code
+
+3. **Add tRPC Procedures**
+   - Define procedures in \`src/server/api/routers/\`
+   - Use type-safe procedures in your React components
+
+4. **Use BOSS**
+   - Run \`./start-boss.sh\` to start BOSS orchestration
+   - BOSS will help you build features following the Spec-Kit workflow
+
+### Documentation
+
+- [T3 Stack Documentation](https://create.t3.gg)
+- [Next.js Documentation](https://nextjs.org/docs)
+- [tRPC Documentation](https://trpc.io/docs)
+- [Prisma Documentation](https://www.prisma.io/docs)
+

package/dist/assets/template-loader/README.md

@@ -0,0 +1,28 @@
+# ${config.name}
+
+BOSS project bootstrapped with template: ${template}
+
+## Getting Started
+
+\`\`\`bash
+# Install dependencies
+pnpm install
+
+# Start infrastructure
+docker-compose up -d
+
+# Run tests
+pnpm test
+
+# Start BOSS
+./start-boss.sh
+\`\`\`
+
+## Project Structure
+
+- \`.boss/\` - BOSS configuration
+- \`.specify/\` - Spec-Kit structure
+- \`.container-use/\` - Container-use configuration
+- \`src/\` - Source code
+- \`tests/\` - Tests
+

package/dist/assets/template-loader/eslint.config.node.js

@@ -0,0 +1,28 @@
+import js from '@eslint/js';
+import tseslint from 'typescript-eslint';
+import globals from 'globals';
+
+export default tseslint.config(
+  js.configs.recommended,
+  ...tseslint.configs.recommended,
+  {
+    files: ['**/*.{ts,js}'],
+    languageOptions: {
+      ecmaVersion: 2022,
+      sourceType: 'module',
+      globals: {
+        ...globals.node,
+        ...globals.es2021,
+      },
+    },
+    rules: {
+      '@typescript-eslint/no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
+      '@typescript-eslint/explicit-function-return-type': 'off',
+      '@typescript-eslint/no-explicit-any': 'warn',
+    },
+  },
+  {
+    ignores: ['dist/**', 'node_modules/**', 'coverage/**', 'build/**'],
+  }
+);
+

package/dist/assets/template-loader/eslint.config.react.js

@@ -0,0 +1,47 @@
+import js from '@eslint/js';
+import tseslint from 'typescript-eslint';
+import react from 'eslint-plugin-react';
+import reactHooks from 'eslint-plugin-react-hooks';
+import globals from 'globals';
+
+export default tseslint.config(
+  js.configs.recommended,
+  ...tseslint.configs.recommended,
+  {
+    files: ['**/*.{ts,tsx,js,jsx}'],
+    plugins: {
+      react,
+      'react-hooks': reactHooks,
+    },
+    languageOptions: {
+      ecmaVersion: 2022,
+      sourceType: 'module',
+      parserOptions: {
+        ecmaFeatures: {
+          jsx: true,
+        },
+      },
+      globals: {
+        ...globals.node,
+        ...globals.browser,
+        ...globals.es2021,
+      },
+    },
+    settings: {
+      react: {
+        version: 'detect',
+      },
+    },
+    rules: {
+      '@typescript-eslint/no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
+      '@typescript-eslint/no-explicit-any': 'warn',
+      'react/react-in-jsx-scope': 'off',
+      'react-hooks/rules-of-hooks': 'error',
+      'react-hooks/exhaustive-deps': 'warn',
+    },
+  },
+  {
+    ignores: ['dist/**', 'node_modules/**', 'coverage/**', '.next/**', 'build/**'],
+  }
+);
+

package/dist/assets/template-loader/gitignore

@@ -0,0 +1,42 @@
+# Dependencies
+node_modules/
+.pnp
+.pnp.js
+
+# Build outputs
+dist/
+build/
+*.tsbuildinfo
+
+# Testing
+coverage/
+.nyc_output/
+
+# Environment variables
+.env
+.env.local
+.env.*.local
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Logs
+logs/
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+# Temporary files
+*.tmp
+*.temp
+

package/dist/assets/template-loader/index.test.ts

@@ -0,0 +1,10 @@
+import { describe, it, expect } from 'vitest';
+import { main } from '../src/index.js';
+
+describe('${config.name}', () => {
+  it('should have a main function', () => {
+    expect(main).toBeDefined();
+    expect(typeof main).toBe('function');
+  });
+});
+

package/dist/assets/template-loader/index.ts

@@ -0,0 +1,13 @@
+/**
+ * ${config.name}
+ * 
+ * Generated by BOSS CLI
+ */
+
+export function main(): void {
+  console.log('Hello from ${config.name}!');
+}
+
+// Uncomment to run when this file is executed directly
+// main();
+

package/dist/assets/template-loader/prettierignore

@@ -0,0 +1,8 @@
+node_modules
+dist
+coverage
+.next
+build
+*.min.js
+*.min.css
+

package/dist/assets/template-loader/vitest.config.ts

@@ -0,0 +1,19 @@
+import { defineConfig } from 'vitest/config';
+
+export default defineConfig({
+  test: {
+    globals: true,
+    environment: 'node',
+    coverage: {
+      provider: 'v8',
+      reporter: ['text', 'json', 'html'],
+      thresholds: {
+        lines: ${coverageThreshold},
+        functions: ${coverageThreshold},
+        branches: ${coverageThreshold},
+        statements: ${coverageThreshold}
+      }
+    }
+  }
+});
+

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

@@ -0,0 +1,106 @@
+# ${workerName} Worker Instructions
+
+## Worker-Specific Guidelines
+
+- 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
+
+## 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 (constitution.md)
+  - Principles established
+  - 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": ["Constitution creation"],
+  "artifactsCreated": [".specify/memory/constitution.md"],
+  "principlesEstablished": ["Test-First", "BDD", "Documentation"],
+  "notes": "Created project constitution with TDD, BDD, and documentation standards"
+}
+```
+
+**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 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"
+
+# Or batch complete architectural phase
+git add .specify/memory/constitution.md .specify/memory/architecture.md
+git commit -m "docs: establish constitution and architectural guidelines"
+```
+
+### Bad Practice ❌
+
+```bash
+# Individual commits for related 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
+
+### Expected Behavior
+
+- **Simple task:** 1-2 commits (constitution + principles)
+- **Complex task:** 2-3 commits (major architectural 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/clarifier/.claude/commands/.gitkeep

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,112 @@
+# ${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
+  - Questions asked/answered
+  - 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": ["Clarification phase"],
+  "artifactsCreated": [".specify/specs/000-requirements/clarification.md"],
+  "questionsAsked": 12,
+  "userPersonasIdentified": 3,
+  "workflowsDocumented": 5,
+  "notes": "Gathered requirements for user authentication feature"
+}
+```
+
+**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 clarification artifacts in one commit
+git add .specify/specs/000-requirements/clarification.md .specify/specs/000-requirements/user-personas.md
+git commit -m "docs: add requirements clarification and user personas"
+
+# Or batch complete requirements gathering
+git add .specify/specs/000-requirements/clarification.md .specify/specs/000-requirements/workflows.md
+git commit -m "docs: complete requirements gathering with clarification and workflows"
+```
+
+### Bad Practice ❌
+
+```bash
+# Individual commits for related work (too granular)
+git add .specify/specs/000-requirements/clarification.md
+git commit -m "docs: add clarification"
+
+git add .specify/specs/000-requirements/user-personas.md
+git commit -m "docs: add personas"
+
+git add .specify/specs/000-requirements/workflows.md
+git commit -m "docs: add workflows"
+```
+
+### Commit Message Format
+
+Follow Conventional Commits:
+- `docs:` - Documentation changes (primary for clarifier)
+- `feat:` - New feature
+- `fix:` - Bug fix
+- `refactor:` - Code refactoring
+
+### Expected Behavior
+
+- **Simple task:** 1-2 commits (initial gathering + refinements)
+- **Complex task:** 2-3 commits (major clarification 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.
+