Claude Skills — Pipeline de Desenvolvimento Modular
chanakarn7/claude-skill
Orquestração doc-driven de projetos modulares com pipeline resumível
Ver no GitHubSistema de skills documentado para orquestrar projetos de software do brainstorming até deploy, com decomposição automática de sistemas grandes em módulos. Oferece pipeline resumível em etapas (BA → SA → UXUI → Prototipagem → Dev → QA → DevOps) com artefatos canonicalizados em Markdown.
Instalação
npx convez-ai chanakarn7/claude-skill1 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 PRD, blueprints técnicos e design system para grandes sistemas
- Coordenar desenvolvimento multi-módulo com rastreamento de progresso
- Padronizar handoff entre fases (requirements → arquitetura → código → testes → deploy)
Veredito

Skill ambicioso de orquestração doc-driven bem pensado para projetos complexos, mas exige disciplina rigorosa com Markdown e decisões iniciais claras. Reduz risco de escopo em sistemas grandes, mas o setup inicial e a curva de adoção são steep para equipes pequenas.
README
A tradução para o português deste README ainda está na fila.
claude-skills
Personal user-level Claude Code skills — a doc-driven delivery pipeline reusable across all projects.
Lives at ~/.claude/skills/ (Mac/Linux) or %USERPROFILE%\.claude\skills\ (Windows).
Pipeline
brainstorm → /ba → /sa → [design direction] → /uxui → /proto → /scaffold → /dev → /qa → /devops
/kickoff orchestrates the whole chain stage-by-stage, enforcing canonical-file hand-offs
(docs/PRD.md → docs/SA_BLUEPRINT.md → docs/UXUI_DESIGN.md → docs/mockups/) and is resumable.
For systems too big for one PRD (ERP, hospital/HIS, marketplace, super-app), /roadmap sits one
level above: it decomposes the system into modules, sizes a rough sprint plan, locks the shared
architecture / data model / design system in docs/program/, then drives /kickoff per module
(writing to docs/modules/<name>/) and tracks progress in docs/program/ROADMAP.md so the whole
multi-sprint build is resumable across many sessions.
Which one? You don't have to choose up front — the skills self-route. /roadmap triages on
entry and hands off to /kickoff if the system turns out small; /kickoff points you up to
/roadmap if it's really multi-module. Rule of thumb: several distinct modules whose data flows
together, shipped across sprints → /roadmap; one coherent project → /kickoff.
Skills
| Skill | Role | Writes |
|---|---|---|
roadmap | program orchestrator for big multi-module/multi-sprint builds (triage → decompose → sprint plan → drive /kickoff per module) | docs/program/{VISION,ARCHITECTURE,DATA_MODEL,DESIGN_SYSTEM,ROADMAP}.md |
kickoff | orchestrator (sizes run, manages token budget, decision points) | — |
ba | requirements → PRD | docs/PRD.md |
sa | technical blueprint (schema, API) | docs/SA_BLUEPRINT.md |
uxui | design system + screens (presents 2–3 direction options before locking) | docs/UXUI_DESIGN.md |
proto | single-file clickable HTML prototype | docs/mockups/*.html |
scaffold | runnable repo skeleton via framework CLIs | repo skeleton |
dev | feature code | source |
qa | test cases / scripts | tests |
devops | Docker, CI/CD, deploy | pipelines |
Setup on a new machine
cd ~/.claude
git clone <this-repo-url> skills
Then install the companion plugins (not stored here — they come from marketplaces):
/plugin marketplace add nextlevelbuilder/ui-ux-pro-max-skill
/plugin install ui-ux-pro-max@ui-ux-pro-max-skill
/plugin marketplace add anthropics/skills # superpowers (brainstorming, TDD, etc.)
/reload-plugins
Optional extras: frontend-design (official, alt design direction), taste (craft enforcement).