IT Project Planner
niki8885/claude-project-planner
Planejamento de projetos IT em 4 estágios: requisitos → pesquisa → MVP → sprints
Ver no GitHubSuite estruturada de skills que guia o Claude pelo ciclo completo de planejamento de projetos IT — desde levantamento de requisitos até arquitetura pronta para sprints e breakdown de tarefas Jira. Inclui 5 skills sequenciais que geram documentação, personas, histórias de usuário, matriz MVP e plano de sprints com diagramas de arquitetura.
Instalação
npx convez-ai niki8885/claude-project-planner1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Estruturar planejamento de novos projetos de software do zero
- Gerar documentação de requisitos e personas automaticamente
- Criar plano de sprints Jira-compatível com estimativas e arquitetura
Veredito

Skill robusto para times que precisam de metodologia estruturada de planejamento. Excelente para documentação e rastreabilidade, mas demanda que o usuário entenda o fluxo sequencial de 4 estágios e tenha clareza nos requisitos iniciais.
README
A tradução para o português deste README ainda está na fila.
IT Project Planner — 4-Stage Planning Suite
A structured skill suite that guides Claude through the full lifecycle of IT project planning — from initial requirements gathering to sprint-ready architecture and Jira task breakdown.
Skills
| Skill | Stage | What it produces |
|---|---|---|
/project-init | Stage 1 | Requirements interview → 3 project variants → confirmed tech stack |
/project-research | Stage 2 | Competitor research, UX personas, hypotheses, value proposition, 25–36 user stories |
/project-interviews | Optional | Simulated UX interviews for each persona — surfaces pain points and contradictions |
/project-mvp | Stage 3 | MVP matrix with Impact/Complexity/Stack Risk scoring, release stages, KPIs |
/project-sprints | Stage 4 | Jira board, epics, sprint plan with typed tasks, system architecture with Mermaid diagrams |
Usage
Run stages in order — each skill validates that the previous stage output is present.
/project-init → define the project, pick a variant
/project-research → competitor research, personas, user stories
/project-interviews → (optional) simulate persona interviews
/project-mvp → prioritize stories, plan releases, set KPIs
/project-sprints → sprint breakdown, task cards, architecture
Each skill accepts the project name as an argument:
/project-init my-app
/project-research my-app
/project-mvp my-app
/project-sprints my-app
Output documents
| Document | Generated by |
|---|---|
[ProjectName]-requirements.md | /project-init |
[ProjectName]-research.md | /project-research |
[ProjectName]-interview-guide.md | /project-research |
[ProjectName]-interviews.md | /project-interviews |
[ProjectName]-mvp.md | /project-mvp |
[ProjectName]-sprints.md | /project-sprints |
[ProjectName]-architecture.md | /project-sprints |
Features
- Language-aware — responds in the user's language; all documents generated in English
- Stack-aware — calibrates complexity, velocity, and capacity to team size and tech stack
- AI-assistance mode —
/project-initexpands the stack and marks AI-assisted components when opted in - Educational vs standalone — separate paths for learning projects vs. production builds
- Mermaid diagrams — architecture output renders in GitHub, Confluence, and Notion
- Jira-compatible — task IDs follow
[PROJ]-Nformat; all task types included (Story/Feature/Spike/Tech Debt/Research/Bug)
License
MIT License — Copyright (c) 2025 Nikita Manaenkov