Skip to content

kanopi/cms-planner

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

11 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

CMS Planner

AI-powered project planning for web development. Generate comprehensive Functional Requirements Documents (FRDs) with story point estimates, Teamwork-ready CSV backlogs, and implementation roadmaps.

What is CMS Planner?

CMS Planner is a Claude Code plugin that transforms project ideas into detailed, actionable Functional Requirements Documents. Perfect for Drupal, WordPress, and recipe-based architectures, it helps you plan projects with:

  • Comprehensive FRDs - Executive summaries, technical requirements, functional specs, and implementation plans
  • Story Point Estimation - Fibonacci-based estimates with hour conversions for budgeting
  • Teamwork Integration - CSV exports with estimated hours ready for direct import
  • Recipe-Based Architecture Support - Special handling for Drupal recipes with shared field storage
  • WordPress Block Theme Expertise - Block/pattern inventory, theme.json specifications, Core Web Vitals performance budgets
  • Risk Assessment - Platform-specific technical and project risk identification with mitigation strategies
  • Success Criteria - Clear functional, technical, and business success metrics

Features

🎯 Project Planning Command

/functional-requirements - Generate comprehensive FRDs with:

  • Project discovery and requirements gathering
  • Technical architecture specifications
  • Story point estimation using Fibonacci sequence
  • Phase-based implementation plans
  • Risk assessment and mitigation strategies
  • Success criteria framework
  • Teamwork-ready CSV backlog export

πŸ“Š What You Get

  1. Functional Requirements Document (Markdown)

    • Executive summary with business objectives
    • Technical requirements with architecture patterns
    • Functional requirements with acceptance criteria
    • UI/UX requirements and accessibility standards
    • Data models and entity relationships
    • Non-functional requirements (performance, security, SEO)
    • Implementation plan with phases and milestones
    • Testing requirements and UAT process
    • Risk assessment matrix
    • Success criteria framework
  2. Teamwork CSV Backlog

    • Phase-based task organization
    • Epic/Story/Task hierarchy
    • Story point estimates in task names and tags
    • Complete ticket descriptions with acceptance criteria
    • Priority levels (high/medium/low)
    • Ready for direct import

πŸ—οΈ Special Support for Recipe-Based Projects

When working with Drupal recipes or similar architectures:

  • Recipe structure guidelines (self-contained configuration entities)
  • Shared field storage documentation
  • Installation order dependencies
  • Recipe naming conventions
  • Demo content integration patterns

Installation

Via Claude Toolbox Marketplace (Recommended)

# Add the Kanopi toolbox marketplace
/plugin marketplace add kanopi/claude-toolbox

# Install CMS Planner
/plugin install cms-planner@claude-toolbox

Direct from GitHub

/plugin install https://github.com/kanopi/cms-planner

Quick Start

Generate an FRD

/functional-requirements

Claude will guide you through:

  1. Discovery - Business objectives, target users, technical constraints
  2. Requirements - Features, priorities, MVP vs future phases
  3. Architecture - Platform, tech stack, patterns
  4. Team - Size, velocity, timeline
  5. Generation - FRD + CSV backlog creation

Example Usage

# Start with project details
/functional-requirements

# Or provide details inline
/functional-requirements I need to build a healthcare website for a hospital system...

Claude will:

  1. Ask clarifying questions about scope, team, timeline
  2. Generate comprehensive FRD with story points
  3. Create Teamwork CSV with phase-based organization
  4. Save files to your project's docs/ directory

Story Point Estimation

CMS Planner uses Fibonacci sequence estimation:

Points Time Examples
1 <2 hours Text changes, config updates
2 2-4 hours Small features, basic components
3 1 day Standard features with testing
5 2-3 days Complex features, integrations
8 3-5 days Major features, architecture decisions
13 1-2 weeks Epic-level work
21 2-3 weeks Large epics
34+ Too large Must be decomposed

Teamwork CSV Format

Generated CSV includes:

  • Tasklist - Phase grouping (e.g., "Phase 1: Setup")
  • Task - Hierarchical naming with story points
  • Description - Complete ticket template with user stories
  • Priority - high/medium/low
  • Tags - SP-X (story points), Phase-X (phase number)
  • Status - Active for all new tasks

Example task hierarchy:

[EPIC] User Management [34 points]
- [STORY] User Registration [13 points]
-- [TASK] Create registration form [5 points]
-- [TASK] Email verification [3 points]
-- [TASK] Password validation [2 points]

Documentation

Full documentation available at: https://kanopi.github.io/cms-planner/

Use Cases

Drupal Recipe-Based Site Templates

Generate FRDs for recipe-based site templates with:

  • Shared field storage documentation
  • Recipe installation order and dependencies
  • Demo content integration patterns
  • Field reuse mapping across content types

WordPress Block Theme Projects

Plan block theme development with specialized deliverables:

  • Block/Pattern Inventory - Decision matrix for core blocks vs patterns vs ACF vs custom Gutenberg blocks
  • theme.json Specifications - Complete v3 configuration (colors, typography, spacing, layout)
  • Performance Budget - Core Web Vitals targets (LCP < 2.5s, INP < 200ms, CLS < 0.1)
  • Plugin Justification - Documented rationale for each plugin (target < 15 plugins)
  • Pattern-First Framework - Enforce cost-effective development approach (patterns 3-10x faster than custom blocks)
  • Hour Estimates - Story points converted to hours for stakeholder budgeting

Client Projects

Create comprehensive project documentation for stakeholder review and team implementation.

Internal Tools

Document internal tool development with clear requirements and success criteria.

Requirements

  • Claude Code (latest version)
  • Access to project files for saving FRDs
  • (Optional) Teamwork account for CSV import

Development

# Clone repository
git clone https://github.com/kanopi/cms-planner.git
cd cms-planner

# Build documentation
pip install zensical
zensical build
zensical serve  # Test locally at http://localhost:8000

# Install in Claude Code
/plugin install /path/to/cms-planner

Contributing

Contributions welcome! Please see CONTRIBUTING.md for guidelines.

License

GPL-2.0-or-later - see LICENSE.md for details

Support

Credits

Developed and maintained by Kanopi Studios.

Related Projects

  • CMS Cultivator - 14 specialized commands + 9 Agent Skills for Drupal and WordPress development
  • Claude Toolbox - Marketplace for Claude Code plugins

Made with ❀️ by Kanopi Studios

About

Claude Code plugin for web development project planning.

Topics

Resources

License

Contributing

Stars

Watchers

Forks

Contributors

Languages