mumucc 0.4.4 → 0.4.10

package/defaults/plugin-seed/marketplaces/claude-code-workflows/plugins/conductor/commands/setup.md

@@ -0,0 +1,406 @@
+---
+description: "Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides)"
+argument-hint: "[--resume]"
+---
+
+# Conductor Setup
+
+Initialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.
+
+## Pre-flight Checks
+
+1. Check if `conductor/` directory already exists in the project root:
+   - If `conductor/product.md` exists: Ask user whether to resume setup or reinitialize
+   - If `conductor/setup_state.json` exists with incomplete status: Offer to resume from last step
+
+2. Detect project type by checking for existing indicators:
+   - **Greenfield (new project)**: No .git, no package.json, no requirements.txt, no go.mod, no src/ directory
+   - **Brownfield (existing project)**: Any of the above exist
+
+3. Load or create `conductor/setup_state.json`:
+   ```json
+   {
+     "status": "in_progress",
+     "project_type": "greenfield|brownfield",
+     "current_section": "product|guidelines|tech_stack|workflow|styleguides",
+     "current_question": 1,
+     "completed_sections": [],
+     "answers": {},
+     "files_created": [],
+     "started_at": "ISO_TIMESTAMP",
+     "last_updated": "ISO_TIMESTAMP"
+   }
+   ```
+
+## Interactive Q&A Protocol
+
+**CRITICAL RULES:**
+
+- Ask ONE question per turn
+- Wait for user response before proceeding
+- Offer 2-3 suggested answers plus "Type your own" option
+- Maximum 5 questions per section
+- Update `setup_state.json` after each successful step
+- Validate file writes succeeded before continuing
+
+### Section 1: Product Definition (max 5 questions)
+
+**Q1: Project Name**
+
+```
+What is your project name?
+
+Suggested:
+1. [Infer from directory name]
+2. [Infer from package.json/go.mod if brownfield]
+3. Type your own
+```
+
+**Q2: Project Description**
+
+```
+Describe your project in one sentence.
+
+Suggested:
+1. A web application that [does X]
+2. A CLI tool for [doing Y]
+3. Type your own
+```
+
+**Q3: Problem Statement**
+
+```
+What problem does this project solve?
+
+Suggested:
+1. Users struggle to [pain point]
+2. There's no good way to [need]
+3. Type your own
+```
+
+**Q4: Target Users**
+
+```
+Who are the primary users?
+
+Suggested:
+1. Developers building [X]
+2. End users who need [Y]
+3. Internal teams managing [Z]
+4. Type your own
+```
+
+**Q5: Key Goals (optional)**
+
+```
+What are 2-3 key goals for this project? (Press enter to skip)
+```
+
+### Section 2: Product Guidelines (max 3 questions)
+
+**Q1: Voice and Tone**
+
+```
+What voice/tone should documentation and UI text use?
+
+Suggested:
+1. Professional and technical
+2. Friendly and approachable
+3. Concise and direct
+4. Type your own
+```
+
+**Q2: Design Principles**
+
+```
+What design principles guide this project?
+
+Suggested:
+1. Simplicity over features
+2. Performance first
+3. Developer experience focused
+4. User safety and reliability
+5. Type your own (comma-separated)
+```
+
+### Section 3: Tech Stack (max 5 questions)
+
+For **brownfield projects**, first analyze existing code:
+
+- Run `Glob` to find package.json, requirements.txt, go.mod, Cargo.toml, etc.
+- Parse detected files to pre-populate tech stack
+- Present findings and ask for confirmation/additions
+
+**Q1: Primary Language(s)**
+
+```
+What primary language(s) does this project use?
+
+[For brownfield: "I detected: Python 3.11, JavaScript. Is this correct?"]
+
+Suggested:
+1. TypeScript
+2. Python
+3. Go
+4. Rust
+5. Type your own (comma-separated)
+```
+
+**Q2: Frontend Framework (if applicable)**
+
+```
+What frontend framework (if any)?
+
+Suggested:
+1. React
+2. Vue
+3. Next.js
+4. None / CLI only
+5. Type your own
+```
+
+**Q3: Backend Framework (if applicable)**
+
+```
+What backend framework (if any)?
+
+Suggested:
+1. Express / Fastify
+2. Django / FastAPI
+3. Go standard library
+4. None / Frontend only
+5. Type your own
+```
+
+**Q4: Database (if applicable)**
+
+```
+What database (if any)?
+
+Suggested:
+1. PostgreSQL
+2. MongoDB
+3. SQLite
+4. None / Stateless
+5. Type your own
+```
+
+**Q5: Infrastructure**
+
+```
+Where will this be deployed?
+
+Suggested:
+1. AWS (Lambda, ECS, etc.)
+2. Vercel / Netlify
+3. Self-hosted / Docker
+4. Not decided yet
+5. Type your own
+```
+
+### Section 4: Workflow Preferences (max 4 questions)
+
+**Q1: TDD Strictness**
+
+```
+How strictly should TDD be enforced?
+
+Suggested:
+1. Strict - tests required before implementation
+2. Moderate - tests encouraged, not blocked
+3. Flexible - tests recommended for complex logic
+```
+
+**Q2: Commit Strategy**
+
+```
+What commit strategy should be followed?
+
+Suggested:
+1. Conventional Commits (feat:, fix:, etc.)
+2. Descriptive messages, no format required
+3. Squash commits per task
+```
+
+**Q3: Code Review Requirements**
+
+```
+What code review policy?
+
+Suggested:
+1. Required for all changes
+2. Required for non-trivial changes
+3. Optional / self-review OK
+```
+
+**Q4: Verification Checkpoints**
+
+```
+When should manual verification be required?
+
+Suggested:
+1. After each phase completion
+2. After each task completion
+3. Only at track completion
+```
+
+### Section 5: Code Style Guides (max 2 questions)
+
+**Q1: Languages to Include**
+
+```
+Which language style guides should be generated?
+
+[Based on detected languages, pre-select]
+
+Options:
+1. TypeScript/JavaScript
+2. Python
+3. Go
+4. Rust
+5. All detected languages
+6. Skip style guides
+```
+
+**Q2: Existing Conventions**
+
+```
+Do you have existing linting/formatting configs to incorporate?
+
+[For brownfield: "I found .eslintrc, .prettierrc. Should I incorporate these?"]
+
+Suggested:
+1. Yes, use existing configs
+2. No, generate fresh guides
+3. Skip this step
+```
+
+## Artifact Generation
+
+After completing Q&A, generate the following files:
+
+### 1. conductor/index.md
+
+```markdown
+# Conductor - [Project Name]
+
+Navigation hub for project context.
+
+## Quick Links
+
+- [Product Definition](./product.md)
+- [Product Guidelines](./product-guidelines.md)
+- [Tech Stack](./tech-stack.md)
+- [Workflow](./workflow.md)
+- [Tracks](./tracks.md)
+
+## Active Tracks
+
+<!-- Auto-populated by /conductor:new-track -->
+
+## Getting Started
+
+Run `/conductor:new-track` to create your first feature track.
+```
+
+### 2. conductor/product.md
+
+Template populated with Q&A answers for:
+
+- Project name and description
+- Problem statement
+- Target users
+- Key goals
+
+### 3. conductor/product-guidelines.md
+
+Template populated with:
+
+- Voice and tone
+- Design principles
+- Any additional standards
+
+### 4. conductor/tech-stack.md
+
+Template populated with:
+
+- Languages (with versions if detected)
+- Frameworks (frontend, backend)
+- Database
+- Infrastructure
+- Key dependencies (for brownfield, from package files)
+
+### 5. conductor/workflow.md
+
+Template populated with:
+
+- TDD policy and strictness level
+- Commit strategy and conventions
+- Code review requirements
+- Verification checkpoint rules
+- Task lifecycle definition
+
+### 6. conductor/tracks.md
+
+```markdown
+# Tracks Registry
+
+| Status | Track ID | Title | Created | Updated |
+| ------ | -------- | ----- | ------- | ------- |
+
+<!-- Tracks registered by /conductor:new-track -->
+```
+
+### 7. conductor/code_styleguides/
+
+Generate selected style guides from `$CLAUDE_PLUGIN_ROOT/templates/code_styleguides/`
+
+## State Management
+
+After each successful file creation:
+
+1. Update `setup_state.json`:
+   - Add filename to `files_created` array
+   - Update `last_updated` timestamp
+   - If section complete, add to `completed_sections`
+2. Verify file exists with `Read` tool
+
+## Completion
+
+When all files are created:
+
+1. Set `setup_state.json` status to "complete"
+2. Display summary:
+
+   ```
+   Conductor setup complete!
+
+   Created artifacts:
+   - conductor/index.md
+   - conductor/product.md
+   - conductor/product-guidelines.md
+   - conductor/tech-stack.md
+   - conductor/workflow.md
+   - conductor/tracks.md
+   - conductor/code_styleguides/[languages]
+
+   Next steps:
+   1. Review generated files and customize as needed
+   2. Run /conductor:new-track to create your first track
+   ```
+
+## Resume Handling
+
+If `--resume` argument or resuming from state:
+
+1. Load `setup_state.json`
+2. Skip completed sections
+3. Resume from `current_section` and `current_question`
+4. Verify previously created files still exist
+5. If files missing, offer to regenerate
+
+## Error Handling
+
+- If file write fails: Halt and report error, do not update state
+- If user cancels: Save current state for future resume
+- If state file corrupted: Offer to start fresh or attempt recovery

package/defaults/plugin-seed/marketplaces/claude-code-workflows/plugins/conductor/commands/status.md

@@ -0,0 +1,319 @@
+---
+description: "Display project status, active tracks, and next actions"
+argument-hint: "[track-id] [--detailed]"
+---
+
+# Conductor Status
+
+Display the current status of the Conductor project, including overall progress, active tracks, and next actions.
+
+## Pre-flight Checks
+
+1. Verify Conductor is initialized:
+   - Check `conductor/product.md` exists
+   - Check `conductor/tracks.md` exists
+   - If missing: Display error and suggest running `/conductor:setup` first
+
+2. Check for any tracks:
+   - Read `conductor/tracks.md`
+   - If no tracks registered: Display setup complete message with suggestion to create first track
+
+## Data Collection
+
+### 1. Project Information
+
+Read `conductor/product.md` and extract:
+
+- Project name
+- Project description
+
+### 2. Tracks Overview
+
+Read `conductor/tracks.md` and parse:
+
+- Total tracks count
+- Completed tracks (marked `[x]`)
+- In-progress tracks (marked `[~]`)
+- Pending tracks (marked `[ ]`)
+
+### 3. Detailed Track Analysis
+
+For each track in `conductor/tracks/`:
+
+Read `conductor/tracks/{trackId}/plan.md`:
+
+- Count total tasks (lines matching `- [x]`, `- [~]`, `- [ ]` with Task prefix)
+- Count completed tasks (`[x]`)
+- Count in-progress tasks (`[~]`)
+- Count pending tasks (`[ ]`)
+- Identify current phase (first phase with incomplete tasks)
+- Identify next pending task
+
+Read `conductor/tracks/{trackId}/metadata.json`:
+
+- Track type (feature, bug, chore, refactor)
+- Created date
+- Last updated date
+- Status
+
+Read `conductor/tracks/{trackId}/spec.md`:
+
+- Check for any noted blockers or dependencies
+
+### 4. Blocker Detection
+
+Scan for potential blockers:
+
+- Tasks marked with `BLOCKED:` prefix
+- Dependencies on incomplete tracks
+- Failed verification tasks
+
+## Output Format
+
+### Full Project Status (no argument)
+
+```
+================================================================================
+                        PROJECT STATUS: {Project Name}
+================================================================================
+Last Updated: {current timestamp}
+
+--------------------------------------------------------------------------------
+                              OVERALL PROGRESS
+--------------------------------------------------------------------------------
+
+Tracks:     {completed}/{total} completed ({percentage}%)
+Tasks:      {completed}/{total} completed ({percentage}%)
+
+Progress:   [##########..........] {percentage}%
+
+--------------------------------------------------------------------------------
+                              TRACK SUMMARY
+--------------------------------------------------------------------------------
+
+| Status | Track ID          | Type    | Tasks      | Last Updated |
+|--------|-------------------|---------|------------|--------------|
+| [x]    | auth_20250110     | feature | 12/12 (100%)| 2025-01-12  |
+| [~]    | dashboard_20250112| feature | 7/15 (47%) | 2025-01-15  |
+| [ ]    | nav-fix_20250114  | bug     | 0/4 (0%)   | 2025-01-14  |
+
+--------------------------------------------------------------------------------
+                              CURRENT FOCUS
+--------------------------------------------------------------------------------
+
+Active Track:  dashboard_20250112 - Dashboard Feature
+Current Phase: Phase 2: Core Components
+Current Task:  [~] Task 2.3: Implement chart rendering
+
+Progress in Phase:
+  - [x] Task 2.1: Create dashboard layout
+  - [x] Task 2.2: Add data fetching hooks
+  - [~] Task 2.3: Implement chart rendering
+  - [ ] Task 2.4: Add filter controls
+
+--------------------------------------------------------------------------------
+                              NEXT ACTIONS
+--------------------------------------------------------------------------------
+
+1. Complete: Task 2.3 - Implement chart rendering (dashboard_20250112)
+2. Then: Task 2.4 - Add filter controls (dashboard_20250112)
+3. After Phase 2: Phase verification checkpoint
+
+--------------------------------------------------------------------------------
+                               BLOCKERS
+--------------------------------------------------------------------------------
+
+{If blockers found:}
+! BLOCKED: Task 3.1 in dashboard_20250112 depends on api_20250111 (incomplete)
+
+{If no blockers:}
+No blockers identified.
+
+================================================================================
+Commands: /conductor:implement {trackId} | /conductor:new-track | /conductor:revert
+================================================================================
+```
+
+### Single Track Status (with track-id argument)
+
+```
+================================================================================
+                    TRACK STATUS: {Track Title}
+================================================================================
+Track ID:    {trackId}
+Type:        {feature|bug|chore|refactor}
+Status:      {Pending|In Progress|Complete}
+Created:     {date}
+Updated:     {date}
+
+--------------------------------------------------------------------------------
+                              SPECIFICATION
+--------------------------------------------------------------------------------
+
+Summary: {brief summary from spec.md}
+
+Acceptance Criteria:
+  - [x] {Criterion 1}
+  - [ ] {Criterion 2}
+  - [ ] {Criterion 3}
+
+--------------------------------------------------------------------------------
+                              IMPLEMENTATION
+--------------------------------------------------------------------------------
+
+Overall:    {completed}/{total} tasks ({percentage}%)
+Progress:   [##########..........] {percentage}%
+
+## Phase 1: {Phase Name} [COMPLETE]
+  - [x] Task 1.1: {description}
+  - [x] Task 1.2: {description}
+  - [x] Verification: {description}
+
+## Phase 2: {Phase Name} [IN PROGRESS]
+  - [x] Task 2.1: {description}
+  - [~] Task 2.2: {description}  <-- CURRENT
+  - [ ] Task 2.3: {description}
+  - [ ] Verification: {description}
+
+## Phase 3: {Phase Name} [PENDING]
+  - [ ] Task 3.1: {description}
+  - [ ] Task 3.2: {description}
+  - [ ] Verification: {description}
+
+--------------------------------------------------------------------------------
+                              GIT HISTORY
+--------------------------------------------------------------------------------
+
+Related Commits:
+  abc1234 - feat: add login form ({trackId})
+  def5678 - feat: add password validation ({trackId})
+  ghi9012 - chore: mark task 1.2 complete ({trackId})
+
+--------------------------------------------------------------------------------
+                              NEXT STEPS
+--------------------------------------------------------------------------------
+
+1. Current: Task 2.2 - {description}
+2. Next: Task 2.3 - {description}
+3. Phase 2 verification pending
+
+================================================================================
+Commands: /conductor:implement {trackId} | /conductor:revert {trackId}
+================================================================================
+```
+
+## Status Markers Legend
+
+Display at bottom if helpful:
+
+```
+Legend:
+  [x] = Complete
+  [~] = In Progress
+  [ ] = Pending
+  [!] = Blocked
+```
+
+## Error States
+
+### No Tracks Found
+
+```
+================================================================================
+                        PROJECT STATUS: {Project Name}
+================================================================================
+
+Conductor is set up but no tracks have been created yet.
+
+To get started:
+  /conductor:new-track "your feature description"
+
+================================================================================
+```
+
+### Conductor Not Initialized
+
+```
+ERROR: Conductor not initialized
+
+Could not find conductor/product.md
+
+Run /conductor:setup to initialize Conductor for this project.
+```
+
+### Track Not Found (with argument)
+
+```
+ERROR: Track not found: {argument}
+
+Available tracks:
+  - auth_20250115
+  - dashboard_20250112
+  - nav-fix_20250114
+
+Usage: /conductor:status [track-id]
+```
+
+## Calculation Logic
+
+### Task Counting
+
+```
+For each plan.md:
+  - Complete: count lines matching /^- \[x\] Task/
+  - In Progress: count lines matching /^- \[~\] Task/
+  - Pending: count lines matching /^- \[ \] Task/
+  - Total: Complete + In Progress + Pending
+```
+
+### Phase Detection
+
+```
+Current phase = first phase header followed by any incomplete task ([ ] or [~])
+```
+
+### Progress Bar
+
+```
+filled = floor((completed / total) * 20)
+empty = 20 - filled
+bar = "[" + "#".repeat(filled) + ".".repeat(empty) + "]"
+```
+
+## Quick Mode
+
+If invoked with `--quick` or `-q`:
+
+```
+{Project Name}: {completed}/{total} tasks ({percentage}%)
+Active: {trackId} - Task {X.Y}
+```
+
+## JSON Output
+
+If invoked with `--json`:
+
+```json
+{
+  "project": "{name}",
+  "timestamp": "ISO_TIMESTAMP",
+  "tracks": {
+    "total": N,
+    "completed": X,
+    "in_progress": Y,
+    "pending": Z
+  },
+  "tasks": {
+    "total": M,
+    "completed": A,
+    "in_progress": B,
+    "pending": C
+  },
+  "current": {
+    "track": "{trackId}",
+    "phase": N,
+    "task": "{X.Y}"
+  },
+  "blockers": []
+}
+```