name: dev-planner
description: >
Generate structured, actionable development plans for Ruby on Rails + Hotwire + Tailwind CSS projects.
Trigger this skill when the user asks to: create a development plan, TODO, implementation roadmap,
sprint plan, build plan, or task breakdown for a web project. Also trigger when the user says
"plan the build", "break this into tasks", "create a TODO", "how do we build this",
"make an implementation plan", or references a Go-to-Market manifest / product spec and wants
a technical execution plan from it. Works alongside backend (Rails) and frontend (Design) skills —
reads the tech stack and constraints from those skills and the project's GTM / product docs

to produce a single, ready-to-execute plan.

Dev Planner

Generate a complete implementation plan (.md file) for a Rails + Hotwire + Tailwind project.

Inputs

Before generating, gather context from available sources:

1. Project docs — GTM manifest, product spec, PRD, or user description in chat. If none provided, ask: "What are we building? Share a product doc or describe the MVP."
2. Backend skill — Read the user's Rails/backend skill (if present in /mnt/skills/user/) to extract stack constraints (Ruby version, DB, queues, caching, auth approach). If absent, use the defaults below.
3. Frontend skill — Read the user's frontend/design skill (if present in /mnt/skills/user/) to extract design constraints (typography, color, motion, composition rules). If absent, use the defaults below.

Default Stack (when backend/frontend skills are not present)

• Ruby on Rails 8, Hotwire (Turbo + Stimulus), Tailwind CSS
• SQLite3, SolidQueue, SolidCable, SolidCache
• rails g authentication for auth
• No unnecessary JavaScript — prefer Turbo Streams
• No Sidekiq, no Redis

Workflow

1. Analyze scope — read all available project context. Determine: what is being built, who are the users, what are the core flows.
2. Estimate complexity — categorize the project:
   • Small (≤ 8 hrs): single-model CRUD, landing page, simple tool.
   • Medium (8–24 hrs): multi-model app, auth, real-time features.
   • Large (24–48+ hrs): multi-module system, API integrations, complex UI.
3. Pick detail level — adapt to complexity and user request:
   • Small → concise plan, no code scaffolds.
   • Medium → phased plan with file structure, DB schema, acceptance criteria.
   • Large → full plan with code scaffolds, hourly breakdown, architecture diagram.
   • If the user explicitly asks for more or less detail, follow their lead.
4. Generate plan — write the .md file following the Plan Template below.
5. Output — save as .md file to /mnt/user-data/outputs/.

Plan Generation Rules

• Language: always English.
• Tech stack: always Rails + Hotwire + Tailwind unless the user explicitly overrides.
• Rails conventions first: prefer generators, concerns, helpers, partials. Mention specific rails g commands where applicable.
• Realistic time estimates: assume a solo developer or small team (2 people). A "day" = ~6 productive hours. Be honest — do not compress unrealistically.
• Prioritize ruthlessly: every plan must have a "Cuts if behind schedule" section with P1 (must), P2 (should), P3 (nice-to-have).
• Acceptance criteria: every phase ends with testable acceptance criteria.
• No fluff: skip motivational text, skip obvious explanations of what Rails is. The reader is a developer.
• File structure: always include a tree view of the final file structure.
• Database schema: include rails g model commands for all models.
• Dependencies: list all gems / npm packages to install.

Adaptive Detail — What to Include

| Section | Small | Medium | Large |
|----------------------|-------|--------|-------|
| Vision Overview | ✅ | ✅ | ✅ |
| Current State | if applicable | ✅ | ✅ |
| Architecture (ASCII) | — | ✅ | ✅ |
| Database Schema | ✅ | ✅ | ✅ |
| Phased Breakdown | checklist only | ✅ | ✅ |
| Hourly Breakdown | — | — | ✅ |
| Code Scaffolds | — | key files | full |
| File Structure | ✅ | ✅ | ✅ |
| Dependencies | ✅ | ✅ | ✅ |
| Cuts If Behind | — | ✅ | ✅ |
| Post-MVP | — | optional | ✅ |
| Success Criteria | ✅ | ✅ | ✅ |

Plan Template

Follow this structure. Skip sections marked as unnecessary for the chosen detail level.

# [Project Name] — Implementation Plan

**Created:** [date]
**Timeline:** [X hours / Y days]
**Objective:** [one sentence — what are we shipping]

---

## Vision Overview

[2–5 sentences. What, who, why.]

- ✅ Differentiator 1
- ✅ Differentiator 2
- ✅ Differentiator 3

---

## Current State                          ← skip for greenfield

**What exists:**
- ✅ [existing feature]

**What's missing:**
- ❌ [missing feature]

---

## Architecture                           ← Medium + Large

┌─────────────────────────────────────┐
│  Browser                            │
│  └── Turbo Frames / Streams         │
└─────────────────────────────────────┘
              ↕ HTTP / WebSocket
┌─────────────────────────────────────┐
│  Rails App                          │
│  ├── Controllers                    │
│  ├── Models + DB (SQLite3)          │
│  ├── Turbo Streams (SolidCable)     │
│  ├── Background Jobs (SolidQueue)   │
│  └── Caching (SolidCache)           │
└─────────────────────────────────────┘

---

## Database Schema

rails g model User email:string:uniq name:string password_digest:string
rails g model Project title:string description:text user:references status:integer

---

## Day N: [Phase Title] ([X hours])

### Phase NA: [Sub-phase] ([Y hours])

**Hour Z: [Task Group]**                  ← Large only

**Tasks:**
- [ ] Task
  - [ ] Sub-task with specific file or command

**Files to create/modify:**               ← Medium (key files) + Large (full)

# app/models/project.rb
class Project < ApplicationRecord
  belongs_to :user
  enum :status, { draft: 0, active: 1, completed: 2 }
  validates :title, presence: true
end

**Acceptance Criteria:**
- [ ] Criterion 1
- [ ] Criterion 2

---

## File Structure

app-name/
├── app/
│   ├── controllers/
│   ├── models/
│   ├── views/
│   └── javascript/controllers/       ← Stimulus
├── config/routes.rb
├── db/migrate/
├── Gemfile
└── README.md

---

## Dependencies

Gemfile:
gem "turbo-rails"
gem "stimulus-rails"
gem "tailwindcss-rails"

Commands:
bundle install
rails db:migrate
bin/dev

---

## Cuts If Behind Schedule               ← Medium + Large

**P1 — Must Have:**
- ✅ [core feature]

**P2 — Should Have:**
- ⚠️ [important but deferrable]

**P3 — Nice to Have:**
- ❌ [can cut entirely]

**Cut from P3 first, then P2.**

---

## Post-MVP                              ← Large or optional

**Week 2:** [next steps]
**Month 2:** [future features]

---

## Success Criteria

**v1.0 is DONE when:**

1. [ ] End-to-end scenario 1
2. [ ] End-to-end scenario 2
3. [ ] End-to-end scenario 3

**If all tests pass → MVP is COMPLETE ✅**

Положи в .claude/SKILLS/dev-planner.md