---
roadcrew_template_name: "README.md"
roadcrew_template_type: "command"
roadcrew_template_version: "v1.0"
roadcrew_last_updated: "2025-11-01"
roadcrew_min_version: "1.5.0"
roadcrew_license: "See LICENSE file in .roadcrew folder"
roadcrew_copyright: "Copyright (c) 2025 North Star Holdings, LLC"
spdx_license_identifier: "LicenseRef-RoadcrewLicense-1.0"
---

# Cursor Commands

> Roadcrew commands organized by workflow stage.

## 🎯 8-Stage Workflow

Roadcrew commands follow a complete development workflow from analysis through publication:

| Stage | Commands | Purpose |
|-------|----------|---------|
| **01 Analysis** | 8 | Repository analysis and documentation |
| **02 Planning** | 9 | Release planning and roadmap management |
| **03 Release** | 6 | Release creation and versioning |
| **04 Implement** | 11 | Epic and issue implementation |
| **05 Code Analysis** | 7 | Code quality and performance audits |
| **06 Testing** | 10 | Testing and validation workflows |
| **07 Publish** | 5 | Distribution and publication |
| **08 Validation** | 4 | Release validation and verification |

**Total:** 60 commands across all stages

### 📁 Directory Structure

```
commands/
├── 01-analysis/                       (8 commands)
│   ├── analyze-repo.md                - Comprehensive repository analysis
│   ├── analyze-multiplatform.md       - Multi-platform project analysis
│   ├── create-brd.md                  - Business Requirements Document
│   ├── create-prd.md                  - Product Requirements Document
│   ├── create-spec.md                 - Technical Specification
│   ├── classify-feedback.md           - Classify customer feedback
│   ├── collect-feedback.md            - Collect feedback from sources
│   ├── minimize-cost.md               - Cost optimization analysis
│   └── README.md
│
├── 02-planning/                       (9 commands)
│   ├── guide-planning.md              - Planning workflow guide
│   ├── create-release-docs.md         - Generate BRD/PRD/Spec
│   ├── advance-release.md             - Advance release status
│   ├── complete-release.md            - Complete release
│   ├── sync-release-status.md         - Sync release status
│   ├── sync-roadmap.md                - Sync roadmap updates
│   ├── update-roadmap.md              - Update roadmap
│   ├── update-my-documents.md         - Update documents
│   └── README.md
│
├── 03-release/                        (6 commands)
│   ├── guide-release.md               - Release workflow guide
│   ├── scope-release.md               - Scope release with issues
│   ├── enrich-release.md              - Enrich release context
│   ├── tag-release.md                 - Tag release version
│   ├── create-release-pr.md           - Create release PR
│   └── README.md
│
├── 04-implement/                      (11 commands)
│   ├── autopilot.md                   - Combined analysis + implementation
│   ├── analyze-epic.md                - Analyze epic structure
│   ├── implement-epic.md              - Implement epic
│   ├── implement-issue.md             - Implement single issue
│   ├── create-epic.md                 - Create new epic
│   ├── generate-module.md             - Generate code module
│   ├── write-tests.md                 - Write tests (TDD)
│   ├── plan-implementation.md         - Plan implementation
│   ├── minimize-manual-steps.md       - Cost optimization
│   ├── usage-report.md                - Usage reporting
│   └── README.md
│
├── 05-code-analysis/                  (7 commands)
│   ├── review-code.md                 - Code review orchestration
│   ├── audit-complexity.md            - Complexity audit
│   ├── audit-security.md              - Security audit
│   ├── audit-performance.md           - Performance audit
│   ├── optimize-command.md            - Command optimization
│   ├── minimize-tokens.md             - Token optimization
│   └── README.md
│
├── 06-testing/                        (10 commands)
│   ├── start-testing.md               - Start testing workflow
│   ├── analyze-test-coverage.md       - Analyze test coverage
│   ├── generate-test-cases.md         - Generate test cases
│   ├── validate-pr.md                 - Validate PR
│   ├── triage-pr.md                   - Triage PR issues
│   ├── validate-github-templates.md   - Validate GitHub templates
│   ├── code-cleanup.md                - Code cleanup
│   ├── uninstall-roadcrew.md          - Uninstall Roadcrew
│   ├── update-roadcrew.md             - Update Roadcrew
│   └── README.md
│
├── 07-publish/                        (5 commands)
│   ├── build-distribution.md          - Build distribution
│   ├── publish-distribution.md        - Publish to public repo
│   ├── update-roadcrew-customer.md    - Customer update guide
│   ├── verify-install.md              - Verify installation
│   └── README.md
│
├── 08-validation/                     (4 commands)
│   ├── validate-release.md            - Validate release
│   ├── validate-release-docs.md       - Validate documentation
│   ├── build-project.md               - Build project
│   └── README.md
│
├── README.md                          - This file
└── environment.json                   - Environment configuration
```

## Quick Start by Use Case

**First time using Roadcrew?**
→ Start with `01-analysis/analyze-repo` to understand your codebase

**Planning a release?**
→ Follow `02-planning/` commands in order: guide-planning → create-release-docs → scope-release

**Implementing features?**
→ Use `04-implement/autopilot [EPIC_NUMBER]` for combined analysis + implementation

**Shipping to customers?**
→ Follow `07-publish/` commands: build-distribution → publish-distribution

**Need to validate quality?**
→ Use `05-code-analysis/` and `06-testing/` commands before merging

## Command Format

Cursor commands are **Markdown (`.md`) files** that provide instructions for Cursor's AI assistant to execute. Each command describes what it does, when to use it, and step-by-step instructions for execution.

## GitHub Authentication

Commands that interact with GitHub (creating issues, PRs, viewing data) require authentication.

**See `.cursorrules.md` (lines 20-25) for:**
- Primary authentication method (GitHub API)
- Backup authentication method (GitHub CLI)
- Required workflow and authentication patterns

## Adding New Commands

To add a new Cursor command:

1. **Create a Markdown file**: `commands/NN-stage/your-command.md`
   - Use a descriptive name with hyphens (kebab-case)
   - Follow the structure of existing command files
   
2. **Document the command**:
   - Title: Clear, action-oriented
   - Description: Brief overview
   - Usage: When and how to run it
   - Process: Step-by-step instructions
   - Examples: Show typical scenarios
   
3. **Update stage README**: Add your command to `NN-stage/README.md`

## Best Practices

- **Keep commands focused**: One clear purpose per command
- **Provide context**: Explain when and why to use it
- **Be explicit**: Give step-by-step instructions for the AI
- **Include examples**: Show expected inputs and outputs
- **Handle errors**: Describe what to do if something fails
- **Test thoroughly**: Verify the command works as documented

## Internal-Only Commands

Development-only commands are stored in `.cursor/internal-only/` and are **not published** to customers. These are used for internal testing, debugging, and admin tasks.

See `.cursor/internal-only/README.md` for details.