Skip to content

Commands Overview

CMS Planner provides a single powerful command for generating comprehensive Functional Requirements Documents with story point estimates and Teamwork-ready backlogs.

Available Commands

/functional-requirements

Generate comprehensive Functional Requirements Documents (FRDs) with: - Interactive project discovery - Technical and functional requirements - Story point estimation (Fibonacci sequence) - Phase-based implementation plans - Risk assessment and success criteria - Teamwork CSV backlog export

Usage: 

/functional-requirements

With inline context: 

/functional-requirements

I'm building a Drupal healthcare site with these requirements:
- Platform: Drupal CMS 2.0+
- Features: Provider directory, services, locations, events
- Team: 3 developers
- Timeline: Launch at DrupalCon Chicago (Feb 2026)

See: Functional Requirements Command Details

Command Philosophy

CMS Planner follows a single, comprehensive command approach:

  • Focused Purpose: FRD generation is a distinct, self-contained task
  • Complete Workflow: All planning logic in one place
  • Interactive Discovery: Guides you through requirements gathering
  • Flexible Input: Accepts inline context or answers questions interactively

Command Features

Interactive Discovery

The command guides you through project discovery by asking about:

  1. Business & Users
  2. Business objectives and success metrics
  3. Target users and their needs

  4. Compliance or regulatory requirements

  5. Technical

  6. Platform, framework, and versions
  7. Architecture patterns
  8. Technical constraints

  9. Integration requirements

  10. Team & Timeline

  11. Team size and composition
  12. Sprint velocity
  13. Timeline and milestones

  14. Resource availability

  15. Scope

  16. Must-have vs nice-to-have features
  17. MVP vs future phases
  18. Priority levels

Smart Context Handling

The command intelligently handles inline context:

  • Acknowledges information you provide upfront
  • Only asks about missing information
  • Allows interruptions for clarifications
  • References provided documentation

Output Files

Generates two files:

  1. FRD Markdown (docs/functional-requirements.md)
  2. Complete requirements specification
  3. Story point estimates
  4. Implementation roadmap
  5. Risk assessment

  6. Success criteria

  7. Teamwork CSV ([project]-backlog-teamwork.csv)

  8. Phase-based organization
  9. Hierarchical tasks (Epic/Story/Task)
  10. Complete descriptions
  11. Story point and phase tags
  12. Ready for direct import

Usage Patterns

Quick Planning

/functional-requirements

Building a WordPress portfolio site for a design agency.
Standard features: portfolio gallery, blog, contact form.
Timeline: 2 months, 2 developers.

Comprehensive Planning

/functional-requirements

Please review existing docs:
- README.md for project overview
- docs/architecture.md for technical decisions

Then generate FRD for Phase 2 development covering:
- E-commerce integration
- Payment processing
- Inventory management
- Shipping calculations

Recipe-Based Projects

/functional-requirements

Drupal recipe-based site template with:
- 8 Saplings recipes (person, service, location, event, etc.)
- Shared field storage (field_phone, field_services, field_department, field_locations)
- Installation order dependencies
- Demo content integration
- Mercury theme subtheming

Next Steps

Getting Help