Features

Built for how engineering teams actually work

dragonPlanner combines structured project data with AI tooling — so planning happens where the work happens.

Claude Integration

Plan and manage work through natural language

dragonPlanner exposes your workspace as an MCP server. Connect it to Claude Code and start planning without switching context.

  • List, create, and update work items from Claude chat
  • Ask for sprint recommendations based on priority and dependencies
  • Generate Jira payloads and sync reference keys automatically
  • Scope access per workspace and project with fine-grained JWT claims
You: What should I work on next in this sprint?

Claude: Based on dependencies and priority, I recommend:

 1. DP-142 — Implement OAuth token refresh
    Priority: High · No blocking deps

 2. DP-138 — Add rate limiting to API
    Priority: High · DP-135 is Done ✓

 3. DP-151 — Write integration tests for auth flow
    Priority: Medium · DP-142 must finish first
Workspace
 └─ Project: Platform API
    ├─ Initiative: Auth & Security
    │  └─ Epic: OAuth 2.0 Integration
    │     ├─ Story: Authorization code flow
    │     │  ├─ Task: Implement PKCE
    │     │  └─ SubTask: Write unit tests
    │     └─ Bug: Token expiry not handled
    │
    └─ Initiative: Performance
       └─ Epic: Database optimization
          └─ Spike: Evaluate read replicas
Work Item Hierarchy

Initiatives down to SubTasks — all connected

Model your delivery tree exactly the way your team thinks. Every level supports dependencies, assignees, and status tracking.

  • 7 item types: Initiative, Epic, Story, Bug, Task, SubTask, Spike
  • Dependency tracking: Blocks, RelatesTo, Duplicate
  • Cascade complete — mark an epic done and close the subtree
  • Priority-aware backlog recommendations
Sprint & PI Planning

Structure work across sprints and program increments

Organize delivery into two-week sprints nested inside quarterly Program Increments. Track velocity, plan capacity, and surface blockers early.

  • Program Increments scoped per workspace and quarter
  • Sprint states: Planning, Active, Completed
  • Holiday calendar support for accurate capacity planning
  • Active sprint detection: by status or today's date
PI 2026 Q1 — Jan 6 → Mar 28

 Sprint 1 · Jan 6–17 · Completed ✓
  12 items · 8 story points delivered

 Sprint 2 · Jan 20–31 · Completed ✓
  10 items · 7 story points delivered

 Sprint 3 · Feb 3–14 · Active ▶
  9 items · 3 in progress · 2 blocked

 Sprint 4 · Feb 17–28 · Planning…
  Capacity: 8 days (MLK holiday excluded)
Claude: I've generated the Jira payload for the
5 unsynced stories in Epic DP-88.

{
  "issueType": "Story",
  "summary": "Implement rate limiting",
  "priority": "High",
  "labels": ["platform", "security"],
  "description": "As an API consumer…"
}

Bulk-update references after import? (y/n)
Jira Sync

Keep Jira in sync without leaving your editor

dragonPlanner stores Jira reference keys on each work item. Claude can generate import-ready payloads and bulk-update keys after you import them — no manual copy-paste.

  • List items not yet synced to Jira
  • Generate Jira-compatible JSON payloads per item
  • Bulk-update JiraKey references after import
  • dragonPlanner never calls Jira directly — your credentials stay yours

Ready to try it?

Free plan includes 1 workspace and full Claude integration.

Coming Soon