claude-code-templates 1.21.1 → 1.21.2

package/cli-tool/components/commands/project-management/create-jtbd.md

@@ -1,37 +0,0 @@
----
-allowed-tools: Read, Write, Edit, Grep, Glob
-argument-hint: [feature-name] | --template | --interactive
-description: Create Jobs-to-be-Done (JTBD) analysis for product features
-model: sonnet
----
-
-# Create Jobs-to-be-Done Document
-
-You are an experienced Product Manager. Create a Jobs to be Done (JTBD) document for a feature we are adding to the product: **$ARGUMENTS**
-
-**IMPORTANT:**
-- Focus on the feature and user needs, not technical implementation
-- Do not include any time estimates
-
-## Required Documentation
-
-1. **Product Documentation**: @product-development/resources/product.md (to understand the product)
-2. **Feature Idea**: @product-development/current-feature/feature.md (to understand the feature idea)
-
-**IMPORTANT**: If you cannot find the feature file, exit the process and notify the user.
-
-## Task
-
-Create a JTBD document that captures the why behind user behavior and focuses on the problem or job the user is trying to get done:
-
-1. Use the JTBD template from `@product-development/resources/JTBD-template.md` 
-2. Based on the feature idea, create a JTBD document that includes:
-   - Job statements following "When [situation], I want [motivation], so I can [expected outcome]"
-   - User needs and pain points analysis  
-   - Desired outcomes from user perspective
-   - Competitive analysis through JTBD lens
-   - Market opportunity assessment
-
-3. Output the JTBD document to `product-development/current-feature/JTBD.md`
-
-Focus on understanding the fundamental jobs users are trying to accomplish rather than technical features.

package/cli-tool/components/commands/project-management/create-prd.md

@@ -1,36 +0,0 @@
----
-allowed-tools: Read, Write, Edit, Grep, Glob
-argument-hint: [feature-name] | --template | --interactive
-description: Create Product Requirements Document (PRD) for new features
-model: sonnet
----
-
-# Create Product Requirements Document
-
-You are an experienced Product Manager. Create a Product Requirements Document (PRD) for a feature we are adding to the product: **$ARGUMENTS**
-
-**IMPORTANT:**
-- Focus on the feature and user needs, not technical implementation
-- Do not include any time estimates
-
-## Product Context
-
-1. **Product Documentation**: @product-development/resources/product.md (to understand the product)
-2. **Feature Documentation**: @product-development/current-feature/feature.md (to understand the feature idea)
-3. **JTBD Documentation**: @product-development/current-feature/JTBD.md (to understand the Jobs to be Done)
-
-## Task
-
-Create a comprehensive PRD document that captures the what, why, and how of the product:
-
-1. Use the PRD template from `@product-development/resources/PRD-template.md`
-2. Based on the feature documentation, create a PRD that defines:
-   - Problem statement and user needs
-   - Feature specifications and scope
-   - Success metrics and acceptance criteria
-   - User experience requirements
-   - Technical considerations (high-level only)
-
-3. Output the completed PRD to `product-development/current-feature/PRD.md`
-
-Focus on creating a comprehensive PRD that clearly defines the feature requirements while maintaining alignment with user needs and business objectives.

package/cli-tool/components/commands/project-management/create-prp.md

@@ -1,37 +0,0 @@
----
-allowed-tools: Read, Write, Edit, WebSearch, Grep, Glob
-argument-hint: [feature-description] | --research | --template | --validate
-description: Create comprehensive Product Requirement Prompt (PRP) with research and validation
-model: sonnet
----
-
-# Create Product Requirement Prompt
-
-Create comprehensive Product Requirement Prompt (PRP) following structured research process: **$ARGUMENTS**
-
-## PRP Foundation
-
-- Base template: @concept_library/cc_PRP_flow/PRPs/base_template_v1
-- PRP concept: @concept_library/cc_PRP_flow/README.md
-- Existing PRPs: !`find concept_library/cc_PRP_flow/PRPs/ -name "*.md" | head -5`
-- Documentation: @ai_docs/ directory analysis
-
-## Task
-
-Develop comprehensive PRP through systematic research and structured documentation:
-
-**Research Process**:
-1. **Documentation Review** - Analyze existing ai_docs/ and project documentation
-2. **Web Research** - Gather implementation examples, library docs, and best practices
-3. **Template Analysis** - Study base_template_v1 structure and existing PRPs
-4. **Codebase Exploration** - Identify patterns, dependencies, and integration points
-5. **Context Synthesis** - Compile comprehensive implementation context
-
-**PRP Development**:
-- Follow base_template_v1 structure exactly
-- Include specific file references and web resources
-- Provide curated codebase intelligence
-- Define clear validation criteria and success metrics
-- Create production-ready implementation guide
-
-**Remember**: PRP = PRD + curated codebase intelligence + agent/runbook—the minimum viable packet an AI needs to ship production-ready code on the first pass.

package/cli-tool/components/commands/project-management/init-project.md

@@ -1,80 +0,0 @@
----
-allowed-tools: Read, Write, Edit, Bash, Glob
-argument-hint: [project-type] [framework] | --react | --vue | --api | --cli
-description: Initialize new project with essential structure, configuration, and development environment setup
-model: sonnet
----
-
-# Initialize New Project
-
-Initialize new project with essential structure: **$ARGUMENTS**
-
-## Instructions
-
-1. **Project Analysis and Setup**
-   - Parse the project type and framework from arguments: `$ARGUMENTS`
-   - If no arguments provided, analyze current directory and ask user for project type and framework
-   - Create project directory structure if needed
-   - Validate that the chosen framework is appropriate for the project type
-
-2. **Base Project Structure**
-   - Create essential directories (src/, tests/, docs/, etc.)
-   - Initialize git repository with proper .gitignore for the project type
-   - Create README.md with project description and setup instructions
-   - Set up proper file structure based on project type and framework
-
-3. **Framework-Specific Configuration**
-   - **Web/React**: Set up React with TypeScript, Vite/Next.js, ESLint, Prettier
-   - **Web/Vue**: Configure Vue 3 with TypeScript, Vite, ESLint, Prettier
-   - **Web/Angular**: Set up Angular CLI project with TypeScript and testing
-   - **API/Express**: Create Express.js server with TypeScript, middleware, and routing
-   - **API/FastAPI**: Set up FastAPI with Python, Pydantic models, and async support
-   - **Mobile/React Native**: Configure React Native with navigation and development tools
-   - **Desktop/Electron**: Set up Electron with renderer and main process structure
-   - **CLI/Node**: Create Node.js CLI with commander.js and proper packaging
-   - **Library/NPM**: Set up library with TypeScript, rollup/webpack, and publishing config
-
-4. **Development Environment Setup**
-   - Configure package manager (npm, yarn, pnpm) with proper package.json
-   - Set up TypeScript configuration with strict mode and path mapping
-   - Configure linting with ESLint and language-specific rules
-   - Set up code formatting with Prettier and pre-commit hooks
-   - Add EditorConfig for consistent coding standards
-
-5. **Testing Infrastructure**
-   - Install and configure testing framework (Jest, Vitest, Pytest, etc.)
-   - Set up test directory structure and example tests
-   - Configure code coverage reporting
-   - Add testing scripts to package.json/makefile
-
-6. **Build and Development Tools**
-   - Configure build system (Vite, webpack, rollup, etc.)
-   - Set up development server with hot reloading
-   - Configure environment variable management
-   - Add build optimization and bundling
-
-7. **CI/CD Pipeline**
-   - Create GitHub Actions workflow for testing and deployment
-   - Set up automated testing on pull requests
-   - Configure automated dependency updates with Dependabot
-   - Add status badges to README
-
-8. **Documentation and Quality**
-   - Generate comprehensive README with installation and usage instructions
-   - Create CONTRIBUTING.md with development guidelines
-   - Set up API documentation generation (JSDoc, Sphinx, etc.)
-   - Add code quality badges and shields
-
-9. **Security and Best Practices**
-   - Configure security scanning with npm audit or similar
-   - Set up dependency vulnerability checking
-   - Add security headers for web applications
-   - Configure environment-specific security settings
-
-10. **Project Validation**
-    - Verify all dependencies install correctly
-    - Run initial build to ensure configuration is working
-    - Execute test suite to validate testing setup
-    - Check linting and formatting rules are applied
-    - Validate that development server starts successfully
-    - Create initial commit with proper project structure

package/cli-tool/components/commands/project-management/milestone-tracker.md

@@ -1,44 +0,0 @@
----
-allowed-tools: Bash, Read, Grep, Glob
-argument-hint: [time-period] | --sprint | --quarter | --all
-description: Track and analyze project milestone progress with predictive analytics
-model: sonnet
----
-
-# Milestone Tracker
-
-Track and monitor project milestone progress with comprehensive analytics: **$ARGUMENTS**
-
-## Current Project Context
-
-- Project activity: !`git log --oneline --since="30 days ago" | wc -l` commits
-- Active branches: !`git branch -r | wc -l` remote branches
-- Recent releases: !`git tag -l --sort=-creatordate | head -5`
-- Milestone data: @.github/milestones/ or Linear integration
-
-## Task
-
-Generate comprehensive milestone tracking report analyzing project delivery progress:
-
-**Time Period**: Use $ARGUMENTS or default to current sprint/quarter
-
-**Analysis Dimensions**:
-1. **Milestone Progress Tracking**
-   - Current milestone completion rates
-   - Velocity trends and burn-down analysis
-   - Critical path identification
-   - Dependency mapping and risk assessment
-
-2. **Predictive Analytics**
-   - Completion date predictions with confidence intervals
-   - Risk-adjusted timeline recommendations
-   - Resource allocation optimization
-   - Scenario planning (what-if analysis)
-
-3. **Health Indicators**
-   - Schedule adherence metrics
-   - Team capacity utilization
-   - Blocker identification and impact
-   - Quality vs delivery balance
-
-**Output**: Interactive milestone dashboard with visual progress indicators, predictive analytics, risk assessments, and actionable recommendations for milestone delivery optimization.

package/cli-tool/components/commands/project-management/pac-configure.md

@@ -1,32 +0,0 @@
----
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: [project-name] | --minimal | --epic-name | --owner
-description: Initialize Product as Code (PAC) project structure with templates and configuration
-model: sonnet
----
-
-# Configure PAC Project
-
-Initialize Product as Code (PAC) project structure: **$ARGUMENTS**
-
-## Current Project State
-
-- Git status: !`git status --porcelain | wc -l` uncommitted changes
-- PAC structure: !`ls -la .pac/ 2>/dev/null | head -5 || echo "No PAC directory"`
-- Existing epics: !`find .pac/epics/ -name "*.yaml" 2>/dev/null | wc -l`
-
-## Task
-
-Configure and initialize PAC project structure for version-controlled product management:
-
-**Setup Process**:
-1. **Project Analysis** - Validate git repository and analyze existing PAC structure
-2. **Directory Creation** - Create `.pac/` structure with epics, tickets, and templates
-3. **Configuration Files** - Generate `pac.config.yaml` with project metadata and defaults
-4. **Template Creation** - Create epic and ticket templates following PAC v0.1.0 specification
-5. **Initial Content** - Create first epic and ticket based on user input
-6. **Integration Setup** - Configure git hooks and validation scripts
-
-**Arguments**: Use --minimal for basic structure, --epic-name for initial epic, --owner for product owner.
-
-**Next Steps**: Use `/project:pac-create-epic` and `/project:pac-create-ticket` to manage product development.

package/cli-tool/components/commands/project-management/pac-create-epic.md

@@ -1,41 +0,0 @@
----
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: [epic-name] | --name | --description | --owner
-description: Create new PAC epic following Product as Code specification
-model: sonnet
----
-
-# Create PAC Epic
-
-Create a new epic following the Product as Code specification with guided workflow: **$ARGUMENTS**
-
-## PAC Configuration Check
-
-- PAC directory: !`ls -la .pac/ 2>/dev/null || echo "No .pac directory found"`
-- PAC config: @.pac/pac.config.yaml (if exists)
-- Existing epics: !`ls -la .pac/epics/ 2>/dev/null | head -10`
-
-## Task
-
-Create a new Product as Code epic:
-
-**Arguments**: 
-- Epic name (required if not using --name flag)
-- --name <name>: Epic name
-- --description <desc>: Epic description  
-- --owner <owner>: Epic owner
-- --scope <scope>: Scope definition
-
-**Epic Creation Process**:
-1. Validate PAC configuration exists (suggest `/project:pac-configure` if missing)
-2. Generate epic ID from name (format: epic-[kebab-case-name])
-3. Create epic YAML file following PAC v0.1.0 specification in `.pac/epics/[epic-id].yaml`
-4. Include required metadata: id, name, created timestamp, owner
-5. Add spec with description, scope, success criteria, constraints, dependencies
-6. Create epic directory structure: `.pac/epics/[epic-id]/`
-7. Update PAC index if `.pac/index.yaml` exists
-8. Create git branch `pac/[epic-id]` if in git repository
-
-If information is missing, prompt user interactively for epic details.
-
-**Next Steps**: Use `/project:pac-create-ticket --epic [epic-id]` to add tickets to this epic.

package/cli-tool/components/commands/project-management/pac-create-ticket.md

@@ -1,42 +0,0 @@
----
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: [ticket-name] | --epic | --type | --assignee | --priority
-description: Create new PAC ticket within an epic following Product as Code specification
-model: sonnet
----
-
-# Create PAC Ticket
-
-Create a new ticket within an epic following Product as Code specification: **$ARGUMENTS**
-
-## PAC Configuration Check
-
-- PAC directory: !`ls -la .pac/ 2>/dev/null || echo "No .pac directory found"`
-- PAC config: @.pac/pac.config.yaml (if exists)
-- Available epics: !`ls -la .pac/epics/ 2>/dev/null | head -10`
-
-## Task
-
-Create a new Product as Code ticket within an existing epic:
-
-**Arguments**:
-- Ticket name (required if not using --name flag)
-- --epic <epic-id>: Parent epic ID (required)
-- --type <type>: Ticket type (feature/bug/task/spike)
-- --assignee <assignee>: Assigned developer
-- --priority <priority>: Priority level
-- --create-branch: Automatically create git branch
-
-**Ticket Creation Process**:
-1. Validate PAC configuration exists (suggest `/project:pac-configure` if missing)
-2. Select or validate parent epic
-3. Generate unique ticket ID and sequence number
-4. Create ticket YAML file following PAC v0.1.0 specification in `.pac/tickets/[ticket-id].yaml`
-5. Include required metadata: id, name, epic, created timestamp, assignee
-6. Add spec with description, type, status, priority, acceptance criteria, tasks
-7. Link ticket to parent epic
-8. Create git branch if requested
-
-If information is missing, prompt user interactively for ticket details.
-
-**Next Steps**: Use `/project:pac-update-status` to track ticket progress.

package/cli-tool/components/commands/project-management/pac-update-status.md

@@ -1,39 +0,0 @@
----
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: [ticket-id] | --status | --assignee | --comment
-description: Update PAC ticket status and track progress in Product as Code workflow
-model: sonnet
----
-
-# Update PAC Ticket Status
-
-Update ticket status and track progress in Product as Code workflow: **$ARGUMENTS**
-
-## PAC Environment Check
-
-- PAC directory: !`ls -la .pac/ 2>/dev/null || echo "No .pac directory found"`
-- Active tickets: !`find .pac/tickets/ -name "*.yaml" 2>/dev/null | wc -l`
-- Recent updates: !`find .pac/tickets/ -name "*.yaml" -mtime -7 2>/dev/null | wc -l`
-
-## Task
-
-Update PAC ticket status and track development progress:
-
-**Arguments**:
-- --ticket <ticket-id>: Ticket ID to update (or select interactively)
-- --status <status>: New status (backlog/in-progress/review/blocked/done/cancelled)
-- --assignee <assignee>: Update assignee
-- --comment <comment>: Add progress comment
-- --epic <epic-id>: Filter tickets by epic for selection
-
-**Status Update Process**:
-1. Validate PAC environment and locate ticket
-2. Load current ticket state and validate status transitions
-3. Update ticket YAML with new status and timestamp
-4. Handle status-specific actions (branch creation, PR suggestions)
-5. Update parent epic with ticket progress
-6. Generate status update summary with next actions
-
-**Valid Status Transitions**: backlog→in-progress→review→done, with blocked/cancelled as intermediate states.
-
-**Git Integration**: Suggests branch creation for in-progress, PR creation for review, and merge for done status.

package/cli-tool/components/commands/project-management/pac-validate.md

@@ -1,35 +0,0 @@
----
-allowed-tools: Read, Bash
-argument-hint: [scope] | --file | --epic | --fix | --pre-commit
-description: Validate Product as Code project structure and files for PAC specification compliance
-model: sonnet
----
-
-# Validate PAC Structure
-
-Validate Product as Code project structure and files for PAC specification compliance: **$ARGUMENTS**
-
-## Current PAC State
-
-- PAC directory: !`ls -la .pac/ 2>/dev/null || echo "No .pac directory found"`
-- Configuration: @.pac/pac.config.yaml (if exists)
-- Epic count: !`find .pac/epics/ -name "*.yaml" 2>/dev/null | wc -l`
-- Ticket count: !`find .pac/tickets/ -name "*.yaml" 2>/dev/null | wc -l`
-
-## Task
-
-Comprehensive validation of PAC project structure and specification compliance:
-
-**Validation Scope**: Use $ARGUMENTS for specific files/epics or validate entire PAC structure
-
-**Validation Checks**:
-1. **Structure Validation** - Directory structure and required files
-2. **Configuration Compliance** - PAC config file format and values
-3. **Epic Validation** - YAML syntax, required fields, and spec compliance
-4. **Ticket Validation** - Format, metadata, and epic references
-5. **Cross-Reference Integrity** - Epic-ticket relationships and dependencies
-6. **Data Consistency** - Timestamps, status transitions, and ID uniqueness
-
-**Output**: Detailed validation report with compliance status, issues found, and specific recommendations for fixes. Use --fix to automatically resolve common issues.
-
-**Exit Codes**: 0 (valid), 1 (errors found), 2 (configuration issues)

package/cli-tool/components/commands/project-management/project-health-check.md

@@ -1,58 +0,0 @@
----
-allowed-tools: Read, Bash, Grep, Glob
-argument-hint: [evaluation-period] | --30-days | --sprint | --quarter
-description: Analyze overall project health and generate comprehensive metrics report
-model: sonnet
----
-
-# Project Health Check
-
-Analyze overall project health and metrics: **$ARGUMENTS**
-
-## Current Project State
-
-- Git activity: !`git log --oneline --since="30 days ago" | wc -l`
-- Contributors: !`git shortlog -sn --since="30 days ago" | head -5`
-- Branch status: !`git branch -r | wc -l` remote branches
-- Code changes: !`git diff --stat HEAD~30 2>/dev/null || echo "Not enough history"`
-- Dependencies: @package.json or @requirements.txt or @Cargo.toml (if exists)
-
-## Task
-
-Generate a comprehensive project health report analyzing:
-
-**Evaluation Period**: Use $ARGUMENTS or default to last 30 days
-
-**Health Dimensions**:
-1. **Code Quality Metrics**
-   - Test coverage and trends
-   - Code complexity analysis
-   - Security vulnerabilities (run npm audit or equivalent)
-   - Technical debt indicators
-
-2. **Delivery Performance**
-   - Sprint velocity trends (if task management tools available)
-   - Cycle time analysis
-   - Bug vs feature ratio
-   - On-time delivery metrics
-
-3. **Team Health Indicators**
-   - PR review turnaround time
-   - Commit frequency distribution
-   - Work distribution balance
-   - Knowledge concentration risk
-
-4. **Dependency Health**
-   - Outdated packages assessment
-   - Security audit results
-   - License compliance check
-   - External service dependencies
-
-**Health Report Format**:
-- Overall health score (0-100) with color-coded status
-- Executive summary with key findings
-- Detailed metrics tables with current vs target values
-- Trend analysis and risk assessment
-- Actionable recommendations prioritized by impact
-
-**Output**: Generate markdown report with charts, metrics tables, and specific action items for improving project health.

package/cli-tool/components/commands/project-management/project-timeline-simulator.md

@@ -1,37 +0,0 @@
----
-allowed-tools: Read, Bash, Grep, Glob
-argument-hint: [project-type] | --duration | --team-size | --risk-level
-description: Simulate project outcomes with variable modeling, risk assessment, and resource optimization
-model: sonnet
----
-
-# Project Timeline Simulator
-
-Simulate project outcomes with comprehensive variable modeling and risk assessment: **$ARGUMENTS**
-
-## Current Project Context
-
-- Project type: Based on $ARGUMENTS or codebase analysis
-- Team capacity: !`git shortlog -sn --since="90 days ago" | wc -l` contributors
-- Velocity data: !`git log --oneline --since="30 days ago" | wc -l` commits/month
-- Risk indicators: @RISKS.md or project documentation
-
-## Task
-
-Generate comprehensive project timeline simulations with multiple scenarios:
-
-**Simulation Framework**:
-1. **Variable Modeling** - Team capacity, skill levels, external dependencies, technical complexity
-2. **Scenario Generation** - Baseline, optimistic, pessimistic, and disruption scenarios
-3. **Risk Assessment** - Technical, resource, business, and external risk factors
-4. **Resource Optimization** - Team allocation, budget distribution, timeline buffers
-5. **Decision Points** - Milestone gates, adaptation triggers, contingency activation
-
-**Output Deliverables**:
-- Timeline prediction ranges with confidence intervals
-- Critical path analysis and dependency mapping
-- Risk-adjusted resource allocation recommendations
-- Early warning indicators and decision triggers
-- Monte Carlo simulation results with probability distributions
-
-**Success Optimization**: Multi-objective optimization for time, quality, and resource efficiency.

package/cli-tool/components/commands/project-management/project-to-linear.md

@@ -1,38 +0,0 @@
----
-allowed-tools: Read, Bash, Grep, Glob
-argument-hint: [project-description] | --team-id | --create-new | --epic-name
-description: Sync project structure and requirements to Linear workspace with comprehensive task breakdown
-model: sonnet
----
-
-# Project to Linear
-
-Sync project structure and requirements to Linear workspace: **$ARGUMENTS**
-
-## Linear Integration Status
-
-- Linear MCP: Check if Linear MCP server is configured
-- Workspace access: !`echo "Test Linear connection if MCP available"`
-- Project context: @README.md or project documentation
-- Requirements: Based on $ARGUMENTS analysis
-
-## Task
-
-Analyze project requirements and create comprehensive Linear task structure:
-
-**Project Analysis Process**:
-1. **Requirement Analysis** - Parse project description and identify major components
-2. **Task Breakdown** - Create hierarchical task structure with epics and subtasks
-3. **Dependency Mapping** - Identify task dependencies and critical path
-4. **Linear Integration** - Create project, epics, and tasks in Linear workspace
-5. **Validation** - Review created structure and provide project overview
-
-**Task Organization**:
-- Epic-level features and major components
-- Parent tasks for feature areas
-- Detailed subtasks with acceptance criteria
-- Proper labeling (frontend, backend, testing, documentation)
-- Priority and effort estimates
-- Timeline and dependency relationships
-
-**Output**: Complete Linear project structure with organized task hierarchy, clear descriptions, and actionable items.

package/cli-tool/components/commands/project-management/release.md

@@ -1,31 +0,0 @@
----
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: [version-type] | --patch | --minor | --major | --prerelease
-description: Prepare and execute project release with version management and changelog updates
-model: sonnet
----
-
-# Project Release
-
-Update CHANGELOG.md with changes since the last version increase. Check our README.md for any necessary changes. Check the scope of changes since the last release and increase our version number as appropriate: **$ARGUMENTS**
-
-## Current Project State
-
-- Git status: !`git status --porcelain`
-- Current version: !`git describe --tags --abbrev=0 2>/dev/null || echo "No previous tags"`
-- Recent commits: !`git log --oneline --since="1 month ago" | head -10`
-- Package info: @package.json or @setup.py or @Cargo.toml (if exists)
-
-## Task
-
-Prepare a project release following these steps:
-
-1. **Analyze Changes**: Review git history since last release to determine appropriate version increment
-2. **Update Version**: Update version in package.json, setup.py, or other version files based on semantic versioning
-3. **Update Changelog**: Add new entries to CHANGELOG.md with proper categorization (Added, Changed, Fixed, etc.)
-4. **Update Documentation**: Review and update README.md if necessary for new features or changes
-5. **Create Release**: Tag the release and prepare release notes
-
-If version type is specified in $ARGUMENTS, use that increment. Otherwise, analyze the changes and suggest appropriate versioning.
-
-Focus on maintaining proper semantic versioning and clear changelog documentation.

package/cli-tool/components/commands/project-management/todo.md

@@ -1,62 +0,0 @@
----
-allowed-tools: Read, Write, Edit
-argument-hint: [action] [task-description] | add | complete | remove | list
-description: Manage project todos in todos.md file
-model: sonnet
----
-
-# Project Todo Manager
-
-Manage todos in a `todos.md` file at the root of your current project directory: **$ARGUMENTS**
-
-## Usage Examples:
-- `/user:todo add "Fix navigation bug"`
-- `/user:todo add "Fix navigation bug" [date/time/"tomorrow"/"next week"]` an optional 2nd parameter to set a due date
-- `/user:todo complete 1` 
-- `/user:todo remove 2`
-- `/user:todo list`
-- `/user:todo undo 1`
-
-## Instructions:
-
-You are a todo manager for the current project. When this command is invoked:
-
-1. **Determine the project root** by looking for common indicators (.git, package.json, etc.)
-2. **Locate or create** `todos.md` in the project root
-3. **Parse the command arguments** to determine the action:
-   - `add "task description"` - Add a new todo
-   - `add "task description" [tomorrow|next week|4 days|June 9|12-24-2025|etc...]` - Add a new todo with the provided due date
-   - `due N [tomorrow|next week|4 days|June 9|12-24-2025|etc...]` - Mark todo N with the due date provided
-   - `complete N` - Mark todo N as completed and move from the ##Active list to the ##Completed list
-   - `remove N` - Remove todo N entirely
-   - `undo N` - Mark completed todo N as incomplete
-   - `list [N]` or no args - Show all (or N number of) todos in a user-friendly format, with each todo numbered for reference
-   - `past due` - Show all of the tasks which are past due and still active
-   - `next` - Shows the next active task in the list, this should respect Due dates, if there are any. If not, just show the first todo in the Active list
-
-## Todo Format:
-Use this markdown format in todos.md:
-```markdown
-# Project Todos
-
-## Active
-- [ ] Task description here | Due: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified)
-- [ ] Another task 
-
-## Completed  
-- [x] Finished task | Done: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified) 
-- [x] Another completed task | Due: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified) | Done: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified) 
-```
-
-## Behavior:
-- Number todos when displaying (1, 2, 3...)
-- Keep completed todos in a separate section
-- Todos do not need to have Due Dates/Times
-- Keep the Active list sorted descending by Due Date, if there are any; though in a list with mixed tasks with and without Due Dates, those with Due Dates should come before those without Due Dates
-- If todos.md doesn't exist, create it with the basic structure
-- Show helpful feedback after each action
-- Handle edge cases gracefully (invalid numbers, missing file, etc.)
-- All provided dates/times should be saved/formatted in a standardized format of MM/DD/YYYY (or DD/MM/YYYY depending on locale), unless the user specifies a different format
-- Times should not be included in the due date format unless requested (`due N in 2 hours` should be MM/DD/YYYY @ [+ 2 hours from now]) 
-
-Always be concise and helpful in your responses.