chiefwiggum 1.0.1 → 1.2.0

package/chiefwiggum

@@ -25,6 +25,10 @@ NC='\033[0m'
 # =========================================
 # CONFIGURATION
 # =========================================
+SCRIPT_DIR="$(dirname "$(realpath "$0")")"
+CHIEFWIGGUM_HOME="${CHIEFWIGGUM_HOME:-$HOME/.chiefwiggum}"
+TEMPLATES_DIR="${CHIEFWIGGUM_HOME}/templates"
+BUNDLED_TEMPLATES="${SCRIPT_DIR}/templates"
 TODO_FILE="${TODO_FILE:-TODO.md}"
 COOLDOWN_SECONDS="${COOLDOWN_SECONDS:-5}"
 
@@ -69,6 +73,10 @@ show_help() {
   echo "  chiefwiggum loop                 # Start build loop"
   echo "  chiefwiggum                      # Same as 'loop'"
   echo ""
+  echo "Templates:"
+  echo -e "  ${CYAN}${TEMPLATES_DIR}${NC}"
+  echo "  Edit these to customize how specs are generated."
+  echo ""
 }
 
 # =========================================
@@ -371,31 +379,43 @@ generate_from_plan() {
   echo -e "${GREEN}  Generating specs from: ${plan_file}${NC}"
   echo -e "${GREEN}════════════════════════════════════════${NC}"
 
+  # Check templates exist
+  if [ ! -d "$TEMPLATES_DIR" ]; then
+    echo -e "${RED}Templates not found at: ${TEMPLATES_DIR}${NC}"
+    echo ""
+    echo "Run this to set up templates:"
+    echo -e "  ${CYAN}npx chiefwiggum@latest${NC}"
+    exit 1
+  fi
+
   mkdir -p specs
 
+  # Load templates
+  local prd_template=$(cat "$TEMPLATES_DIR/specs/prd.md")
+  local tech_template=$(cat "$TEMPLATES_DIR/specs/technical.md")
+  local todo_template=$(cat "$TEMPLATES_DIR/TODO.md")
+  local claude_template=$(cat "$TEMPLATES_DIR/CLAUDE.md")
+
   # Step 1: Generate PRD
   echo ""
   echo -e "${YELLOW}[1/4] Generating specs/prd.md...${NC}"
 
-  local prd_prompt="You are generating a PRD (Product Requirements Document) from a project plan.
+  local prd_prompt="You are filling in a PRD template based on a project plan.
 
 Here is the plan:
 <plan>
 ${plan_content}
 </plan>
 
-Generate a complete PRD with these sections:
-- Overview
-- Problem Statement
-- Goals & Success Metrics
-- User Stories
-- Functional Requirements
-- Non-Functional Requirements
-- Out of Scope
+Here is the template to fill in:
+<template>
+${prd_template}
+</template>
 
-Write it directly to specs/prd.md.
-Do NOT ask questions — infer everything from the plan.
-Be concise but comprehensive."
+Fill in the template with specific details from the plan.
+Replace all placeholder text in [brackets] with real content.
+Write the completed PRD directly to specs/prd.md.
+Do NOT ask questions — infer everything from the plan."
 
   echo "$prd_prompt" | claude -p --dangerously-skip-permissions 2>/dev/null
   echo -e "${GREEN}  ✓ specs/prd.md${NC}"
@@ -406,23 +426,21 @@ Be concise but comprehensive."
   local prd_generated
   prd_generated="$(cat specs/prd.md 2>/dev/null || echo "")"
 
-  local tech_prompt="You are generating a Technical Specification from a PRD.
+  local tech_prompt="You are filling in a Technical Specification template based on a PRD.
 
 Here is the PRD:
 <prd>
 ${prd_generated}
 </prd>
 
-Generate a complete Technical Specification with:
-- Architecture Overview
-- Tech Stack
-- Data Model
-- API Design (if applicable)
-- Key Components
-- Security Considerations
-- Performance Considerations
+Here is the template to fill in:
+<template>
+${tech_template}
+</template>
 
-Write it directly to specs/technical.md.
+Fill in the template with specific technical details.
+Replace all placeholder text in [brackets] with real content.
+Write the completed spec directly to specs/technical.md.
 Do NOT ask questions — infer everything from the PRD."
 
   echo "$tech_prompt" | claude -p --dangerously-skip-permissions 2>/dev/null
@@ -435,7 +453,7 @@ Do NOT ask questions — infer everything from the PRD."
   else
     echo -e "${YELLOW}[3/4] Generating CLAUDE.md...${NC}"
 
-    local claude_prompt="You are generating a CLAUDE.md file for a project.
+    local claude_prompt="You are filling in a CLAUDE.md template for a project.
 
 Here is the PRD:
 <prd>
@@ -447,15 +465,15 @@ Here is the Technical Spec:
 $(cat specs/technical.md 2>/dev/null || echo "")
 </technical>
 
-Generate a CLAUDE.md with:
-- Brief project overview
-- Key commands to run
-- Architecture summary
-- Important conventions
-- Empty '## Learnings' section at the bottom
+Here is the template to fill in:
+<template>
+${claude_template}
+</template>
 
-Write it directly to CLAUDE.md.
-Keep it concise - this is a quick reference for AI agents."
+Fill in the template with project-specific details.
+Replace all placeholder text in [brackets] with real content.
+Keep it concise - this is a quick reference for AI agents.
+Write directly to CLAUDE.md."
 
     echo "$claude_prompt" | claude -p --dangerously-skip-permissions 2>/dev/null
     echo -e "${GREEN}  ✓ CLAUDE.md${NC}"
@@ -465,7 +483,7 @@ Keep it concise - this is a quick reference for AI agents."
   echo ""
   echo -e "${YELLOW}[4/4] Generating TODO.md...${NC}"
 
-  local todo_prompt="You are generating a TODO task list from a PRD and Technical Specification.
+  local todo_prompt="You are filling in a TODO template based on specs.
 
 Here is the PRD:
 <prd>
@@ -477,14 +495,16 @@ Here is the Technical Specification:
 $(cat specs/technical.md 2>/dev/null || echo "")
 </technical>
 
-Generate a phased TODO.md with:
-- Logical phases (Setup, Core Features, Polish, etc.)
-- Granular tasks using checkbox format: - [ ] Task description
-- Each phase ends with: - [ ] Phase review
-- Tasks should be completable in 1-2 hours max
+Here is the template to follow:
+<template>
+${todo_template}
+</template>
 
-Write it directly to TODO.md.
-Do NOT ask questions — infer everything from the specs."
+Create a phased TODO.md following the template structure.
+Use checkbox format: - [ ] Task description
+Keep tasks granular (1-2 hours max each).
+End each phase with: - [ ] Phase N review
+Write directly to TODO.md."
 
   echo "$todo_prompt" | claude -p --dangerously-skip-permissions 2>/dev/null
   echo -e "${GREEN}  ✓ TODO.md${NC}"
@@ -493,7 +513,9 @@ Do NOT ask questions — infer everything from the specs."
   echo -e "${GREEN}Specs generated:${NC}"
   echo "  - specs/prd.md"
   echo "  - specs/technical.md"
-  echo "  - CLAUDE.md"
+  if [ ! -f "CLAUDE.md" ]; then
+    echo "  - CLAUDE.md"
+  fi
   echo "  - TODO.md"
 
   # Commit specs
@@ -690,6 +712,18 @@ cleanup_stale_processes() {
   sleep 1
 }
 
+# =========================================
+# SETUP TEMPLATES
+# =========================================
+setup_templates() {
+  # Copy bundled templates to ~/.chiefwiggum/templates
+  if [ -d "$BUNDLED_TEMPLATES" ]; then
+    mkdir -p "$CHIEFWIGGUM_HOME"
+    cp -r "$BUNDLED_TEMPLATES" "$CHIEFWIGGUM_HOME/"
+    echo -e "${GREEN}✓ Templates installed to: ${TEMPLATES_DIR}${NC}"
+  fi
+}
+
 # =========================================
 # INSTALL COMMAND
 # =========================================
@@ -704,6 +738,8 @@ cmd_install() {
     local installed_path=$(which chiefwiggum)
     if [[ "$installed_path" != *"npx"* ]] && [[ "$installed_path" != *".npm/_npx"* ]]; then
       echo -e "${GREEN}✓ Already installed at: ${installed_path}${NC}"
+      # Still set up templates in case they're missing
+      setup_templates
       echo ""
       echo "Run 'chiefwiggum new' to get started."
       return 0
@@ -715,11 +751,23 @@ cmd_install() {
   echo ""
 
   if npm install -g chiefwiggum; then
+    echo ""
+    # Set up templates after install
+    # Need to get the installed location
+    local installed_dir=$(dirname "$(realpath "$(which chiefwiggum)")")
+    if [ -d "${installed_dir}/templates" ]; then
+      mkdir -p "$CHIEFWIGGUM_HOME"
+      cp -r "${installed_dir}/templates" "$CHIEFWIGGUM_HOME/"
+      echo -e "${GREEN}✓ Templates installed to: ${TEMPLATES_DIR}${NC}"
+    fi
+
     echo ""
     echo -e "${GREEN}════════════════════════════════════════${NC}"
     echo -e "${GREEN}  ✓ Installation complete!${NC}"
     echo -e "${GREEN}════════════════════════════════════════${NC}"
     echo ""
+    echo -e "Templates: ${CYAN}${TEMPLATES_DIR}${NC}"
+    echo ""
     echo "Get started:"
     echo -e "  ${CYAN}chiefwiggum new${NC}     # Set up a new project"
     echo -e "  ${CYAN}chiefwiggum loop${NC}    # Run the build loop"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chiefwiggum",
-  "version": "1.0.1",
+  "version": "1.2.0",
   "description": "Autonomous coding agent CLI. Point it at a plan, watch it build.",
   "bin": {
     "chiefwiggum": "./chiefwiggum"

package/templates/CLAUDE.md

@@ -0,0 +1,31 @@
+# CLAUDE.md
+
+## Overview
+
+[Brief project description]
+
+## Commands
+
+```bash
+# Development
+[dev command]
+
+# Build
+[build command]
+
+# Test
+[test command]
+```
+
+## Architecture
+
+[Key architectural decisions and patterns]
+
+## Conventions
+
+- [Convention 1]
+- [Convention 2]
+
+## Learnings
+
+<!-- Add learnings here as you discover them -->

package/templates/TODO.md

@@ -0,0 +1,29 @@
+# TODO
+
+## Phase 1: Setup
+
+- [ ] Initialize project structure
+- [ ] Set up development environment
+- [ ] Configure dependencies
+- [ ] Phase 1 review
+
+## Phase 2: Core Features
+
+- [ ] Implement feature 1
+- [ ] Implement feature 2
+- [ ] Add tests for core features
+- [ ] Phase 2 review
+
+## Phase 3: Polish
+
+- [ ] Add error handling
+- [ ] Improve UX
+- [ ] Performance optimization
+- [ ] Phase 3 review
+
+## Phase 4: Launch
+
+- [ ] Final testing
+- [ ] Documentation
+- [ ] Deployment
+- [ ] Phase 4 review

package/templates/specs/prd.md

@@ -0,0 +1,46 @@
+# Product Requirements Document
+
+## Overview
+
+[Brief description of the product/feature]
+
+## Problem Statement
+
+[What problem does this solve? Why does it matter?]
+
+## Goals & Success Metrics
+
+- [ ] Goal 1
+- [ ] Goal 2
+
+## User Stories
+
+### As a [user type]
+- I want to [action]
+- So that [benefit]
+
+## Functional Requirements
+
+### Core Features
+
+1. **Feature 1**
+   - Description
+   - Acceptance criteria
+
+2. **Feature 2**
+   - Description
+   - Acceptance criteria
+
+## Non-Functional Requirements
+
+- **Performance**: [targets]
+- **Security**: [requirements]
+- **Scalability**: [considerations]
+
+## Out of Scope
+
+- [What we're NOT building]
+
+## Open Questions
+
+- [Unresolved questions]

package/templates/specs/technical.md

@@ -0,0 +1,74 @@
+# Technical Specification
+
+## Architecture Overview
+
+[High-level architecture diagram or description]
+
+## Tech Stack
+
+- **Frontend**:
+- **Backend**:
+- **Database**:
+- **Infrastructure**:
+
+## Data Model
+
+### Entities
+
+```
+Entity1
+├── id
+├── field1
+└── field2
+
+Entity2
+├── id
+├── field1
+└── entity1_id (FK)
+```
+
+## API Design
+
+### Endpoints
+
+| Method | Path | Description |
+|--------|------|-------------|
+| GET | /api/resource | List resources |
+| POST | /api/resource | Create resource |
+
+## Key Components
+
+### Component 1
+
+- **Purpose**:
+- **Responsibilities**:
+- **Dependencies**:
+
+### Component 2
+
+- **Purpose**:
+- **Responsibilities**:
+- **Dependencies**:
+
+## Security Considerations
+
+- Authentication:
+- Authorization:
+- Data protection:
+
+## Performance Considerations
+
+- Caching strategy:
+- Database optimization:
+- Load handling:
+
+## Dependencies
+
+- [External services/APIs]
+- [Third-party libraries]
+
+## Deployment
+
+- Environment setup
+- CI/CD pipeline
+- Monitoring