jordan/rdev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
main
rdev/docs/guides/sdlc/command-catalog.md
jordan 56e3f83955 feat: add auth scopes, OpenAPI docs, SDLC guides, and code quality improvements 
- Add auth.RequireScope() to all handler routes for proper authorization
- Add SDLC OpenAPI endpoint documentation (state, features, tasks, branches, merge, archive, orchestrator)
- Add SDLC documentation guides (getting-started, cli-reference, api-reference, command-catalog)
- Add artifact_test.go for SDLC artifact coverage
- Add CLAUDE.md rules: auth scopes requirement, error wrapping with %w
- Fix error wrapping to use %w instead of %v throughout codebase
- Improve CLI merge command with conflict detection and resolution
- Fix handler tests to include auth middleware for RequireScope
- Add cookbook tree runner scripts for automated testing

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-02 13:55:50 -07:00

2.9 KiB
Raw Permalink Blame History

SDLC Command Catalog

Claude Code commands for SDLC orchestration. These commands are available in projects with the skeleton template.

Feature Lifecycle Commands

/create-feature <slug>

Create a new feature in draft phase.

Example: /create-feature auth-flow

/spec-feature <slug>

Write the specification document for a feature. Creates .sdlc/features/<slug>/spec.md.

/design-feature <slug>

Write the design document for a feature. Creates .sdlc/features/<slug>/design.md.

/breakdown-feature <slug>

Create the task breakdown for a feature. Creates .sdlc/features/<slug>/tasks.md.

/create-qa-plan <slug>

Create the QA test plan for a feature. Creates .sdlc/features/<slug>/qa-plan.md.

Implementation Commands

/implement-task <slug> <task-id>

Implement a specific task from the feature breakdown.

Flow:

  1. Start the task via CLI
  2. Load context (spec, design, tasks)
  3. Study existing patterns
  4. Implement code changes
  5. Run tests
  6. Complete the task

/review-feature <slug>

Perform code review of a feature. Creates .sdlc/features/<slug>/review.md.

/audit-feature <slug>

Perform security audit of a feature. Creates .sdlc/features/<slug>/audit.md.

/run-qa <slug>

Execute the QA test plan for a feature. Creates .sdlc/features/<slug>/qa-results.md.

Merge and Archive Commands

/merge-feature <slug>

Merge a completed feature branch.

Prerequisites:

  • All required artifacts approved (review, audit, qa_results)
  • No blockers
  • Feature in merge phase

Flow:

  1. Check merge readiness
  2. Verify branch status
  3. Run final tests
  4. Execute merge via sdlc merge
  5. Report results

/archive-feature <slug>

Archive a released feature.

Prerequisites:

  • Feature must be in released phase

Query Commands

/sdlc-status

Show the current SDLC state and active features.

/next-action <slug>

Get the classifier's recommended next action for a feature.

Artifact Commands

/approve-artifact <slug> <type>

Approve a feature artifact.

Types: spec, design, tasks, qa_plan, review, audit, qa_results

/reject-artifact <slug> <type>

Reject a feature artifact.

Command Arguments

Argument Description Example
<slug> Feature identifier (lowercase, hyphens) auth-flow
<task-id> Task identifier task-001
<type> Artifact type spec, design, review

Typical Workflow

  1. /create-feature my-feature
  2. /spec-feature my-feature -> Approve spec
  3. /design-feature my-feature -> Approve design
  4. /breakdown-feature my-feature -> Approve tasks
  5. /create-qa-plan my-feature -> Approve QA plan
  6. /implement-task my-feature task-001 (repeat for each task)
  7. /review-feature my-feature -> Approve review
  8. /audit-feature my-feature -> Approve audit
  9. /run-qa my-feature -> QA passes
  10. /merge-feature my-feature
  11. /archive-feature my-feature