up-cc 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/agents/up-depurador.md +357 -0
- package/agents/up-executor.md +409 -0
- package/agents/up-pesquisador-projeto.md +358 -0
- package/agents/up-planejador.md +390 -0
- package/agents/up-roteirista.md +401 -0
- package/agents/up-sintetizador.md +232 -0
- package/agents/up-verificador.md +357 -0
- package/bin/install.js +709 -0
- package/bin/lib/core.cjs +270 -0
- package/bin/up-tools.cjs +1361 -0
- package/commands/adicionar-fase.md +33 -0
- package/commands/ajuda.md +131 -0
- package/commands/discutir-fase.md +35 -0
- package/commands/executar-fase.md +40 -0
- package/commands/novo-projeto.md +39 -0
- package/commands/pausar.md +33 -0
- package/commands/planejar-fase.md +43 -0
- package/commands/progresso.md +33 -0
- package/commands/rapido.md +40 -0
- package/commands/remover-fase.md +34 -0
- package/commands/retomar.md +35 -0
- package/commands/verificar-trabalho.md +35 -0
- package/package.json +32 -0
- package/references/checkpoints.md +358 -0
- package/references/git-integration.md +208 -0
- package/references/questioning.md +156 -0
- package/references/ui-brand.md +124 -0
- package/templates/config.json +6 -0
- package/templates/continue-here.md +78 -0
- package/templates/project.md +184 -0
- package/templates/requirements.md +129 -0
- package/templates/roadmap.md +131 -0
- package/templates/state.md +130 -0
- package/templates/summary.md +174 -0
- package/workflows/discutir-fase.md +324 -0
- package/workflows/executar-fase.md +277 -0
- package/workflows/executar-plano.md +192 -0
- package/workflows/novo-projeto.md +561 -0
- package/workflows/pausar.md +111 -0
- package/workflows/planejar-fase.md +208 -0
- package/workflows/progresso.md +226 -0
- package/workflows/rapido.md +209 -0
- package/workflows/retomar.md +231 -0
- package/workflows/verificar-trabalho.md +261 -0
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:adicionar-fase
|
|
3
|
+
description: Adicionar fase ao final do roadmap
|
|
4
|
+
argument-hint: "<descricao>"
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Write
|
|
8
|
+
- Edit
|
|
9
|
+
- Bash
|
|
10
|
+
- Glob
|
|
11
|
+
---
|
|
12
|
+
<objective>
|
|
13
|
+
Add a new phase to the end of the project roadmap.
|
|
14
|
+
|
|
15
|
+
**Flow:** Parse description -> Call `up-tools.cjs phase add` -> Update STATE.md -> Present result
|
|
16
|
+
</objective>
|
|
17
|
+
|
|
18
|
+
<execution_context>
|
|
19
|
+
@~/.claude/up/workflows/adicionar-fase.md
|
|
20
|
+
</execution_context>
|
|
21
|
+
|
|
22
|
+
<context>
|
|
23
|
+
Phase description: $ARGUMENTS
|
|
24
|
+
|
|
25
|
+
Adds a new phase to ROADMAP.md at the end of the existing phase list.
|
|
26
|
+
</context>
|
|
27
|
+
|
|
28
|
+
<process>
|
|
29
|
+
1. Parse the phase description from arguments.
|
|
30
|
+
2. Call `up-tools.cjs phase add` with the description.
|
|
31
|
+
3. Update STATE.md to reflect the new phase.
|
|
32
|
+
4. Present the result showing the new roadmap state.
|
|
33
|
+
</process>
|
|
@@ -0,0 +1,131 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:ajuda
|
|
3
|
+
description: Referencia de comandos UP
|
|
4
|
+
argument-hint: ""
|
|
5
|
+
allowed-tools: []
|
|
6
|
+
---
|
|
7
|
+
<objective>
|
|
8
|
+
Exibir a referencia completa de comandos UP.
|
|
9
|
+
</objective>
|
|
10
|
+
|
|
11
|
+
<context>
|
|
12
|
+
Referencia inline -- nenhum arquivo externo necessario.
|
|
13
|
+
</context>
|
|
14
|
+
|
|
15
|
+
<process>
|
|
16
|
+
Exiba a referencia abaixo EXATAMENTE como esta, formatada em markdown:
|
|
17
|
+
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
# UP -- Referencia de Comandos
|
|
21
|
+
|
|
22
|
+
Sistema de desenvolvimento orientado a fases para projetos de software.
|
|
23
|
+
|
|
24
|
+
## Comandos Disponiveis
|
|
25
|
+
|
|
26
|
+
### Inicializacao
|
|
27
|
+
|
|
28
|
+
| Comando | Descricao | Uso |
|
|
29
|
+
|---------|-----------|-----|
|
|
30
|
+
| `/up:novo-projeto` | Inicializar novo projeto com coleta de contexto | `/up:novo-projeto` |
|
|
31
|
+
| `/up:retomar` | Restaurar contexto da sessao anterior | `/up:retomar` |
|
|
32
|
+
|
|
33
|
+
### Ciclo de Fase
|
|
34
|
+
|
|
35
|
+
| Comando | Descricao | Uso |
|
|
36
|
+
|---------|-----------|-----|
|
|
37
|
+
| `/up:discutir-fase` | Coletar contexto por questionamento | `/up:discutir-fase 1` |
|
|
38
|
+
| `/up:planejar-fase` | Planejar fase com research e self-check | `/up:planejar-fase 1` |
|
|
39
|
+
| `/up:executar-fase` | Executar planos com paralelizacao por ondas | `/up:executar-fase 1` |
|
|
40
|
+
| `/up:verificar-trabalho` | Validar features via UAT conversacional | `/up:verificar-trabalho 1` |
|
|
41
|
+
|
|
42
|
+
### Gerenciamento
|
|
43
|
+
|
|
44
|
+
| Comando | Descricao | Uso |
|
|
45
|
+
|---------|-----------|-----|
|
|
46
|
+
| `/up:progresso` | Status do projeto e proxima acao | `/up:progresso` |
|
|
47
|
+
| `/up:pausar` | Criar handoff .continue-aqui.md | `/up:pausar` |
|
|
48
|
+
| `/up:adicionar-fase` | Adicionar fase ao roadmap | `/up:adicionar-fase "Deploy em producao"` |
|
|
49
|
+
| `/up:remover-fase` | Remover fase futura e renumerar | `/up:remover-fase 5` |
|
|
50
|
+
|
|
51
|
+
### Utilitarios
|
|
52
|
+
|
|
53
|
+
| Comando | Descricao | Uso |
|
|
54
|
+
|---------|-----------|-----|
|
|
55
|
+
| `/up:rapido` | Tarefa rapida com garantias UP | `/up:rapido "Corrigir bug no login"` |
|
|
56
|
+
| `/up:ajuda` | Esta referencia | `/up:ajuda` |
|
|
57
|
+
|
|
58
|
+
## Flags Comuns
|
|
59
|
+
|
|
60
|
+
### planejar-fase
|
|
61
|
+
- `--pesquisar` -- Forcar re-pesquisa mesmo se RESEARCH.md existir
|
|
62
|
+
- `--sem-pesquisa` -- Pular pesquisa, ir direto ao planejamento
|
|
63
|
+
- `--auto` -- Auto-detectar proxima fase nao planejada
|
|
64
|
+
- `--gaps` -- Modo fechamento de gaps (le VERIFICATION.md)
|
|
65
|
+
|
|
66
|
+
### executar-fase
|
|
67
|
+
- `--gaps-only` -- Executar apenas planos de fechamento de gaps
|
|
68
|
+
|
|
69
|
+
## Estrutura do Diretorio .plano/
|
|
70
|
+
|
|
71
|
+
```
|
|
72
|
+
.plano/
|
|
73
|
+
STATE.md # Estado atual do projeto
|
|
74
|
+
ROADMAP.md # Roadmap com todas as fases
|
|
75
|
+
fase-01-nome/
|
|
76
|
+
CONTEXT.md # Contexto coletado na discussao
|
|
77
|
+
RESEARCH.md # Pesquisa de dominio/tecnologia
|
|
78
|
+
PLAN-001.md # Plano executavel
|
|
79
|
+
PLAN-002.md # Outro plano da fase
|
|
80
|
+
VERIFICATION.md # Resultado da verificacao
|
|
81
|
+
fase-02-nome/
|
|
82
|
+
...
|
|
83
|
+
rapido/
|
|
84
|
+
TASK-001.md # Tarefa rapida executada
|
|
85
|
+
...
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
## Fluxos de Trabalho Comuns
|
|
89
|
+
|
|
90
|
+
### Novo Projeto (do zero)
|
|
91
|
+
```
|
|
92
|
+
/up:novo-projeto
|
|
93
|
+
/up:discutir-fase 1
|
|
94
|
+
/up:planejar-fase 1
|
|
95
|
+
/up:executar-fase 1
|
|
96
|
+
/up:verificar-trabalho 1
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
### Continuar Projeto Existente
|
|
100
|
+
```
|
|
101
|
+
/up:retomar
|
|
102
|
+
/up:progresso
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
### Correcao Rapida
|
|
106
|
+
```
|
|
107
|
+
/up:rapido "Descricao da tarefa"
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
### Pausar e Retomar
|
|
111
|
+
```
|
|
112
|
+
/up:pausar # Ao pausar
|
|
113
|
+
/up:retomar # Na proxima sessao
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
### Adicionar/Remover Fases
|
|
117
|
+
```
|
|
118
|
+
/up:adicionar-fase "Descricao da nova fase"
|
|
119
|
+
/up:remover-fase 5
|
|
120
|
+
```
|
|
121
|
+
|
|
122
|
+
### Ciclo de Fechamento de Gaps
|
|
123
|
+
```
|
|
124
|
+
/up:verificar-trabalho 1 # Identifica gaps
|
|
125
|
+
/up:planejar-fase 1 --gaps # Planeja correcoes
|
|
126
|
+
/up:executar-fase 1 --gaps-only # Executa correcoes
|
|
127
|
+
/up:verificar-trabalho 1 # Re-verifica
|
|
128
|
+
```
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
</process>
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:discutir-fase
|
|
3
|
+
description: Coletar contexto da fase por questionamento antes do planejamento
|
|
4
|
+
argument-hint: "<fase>"
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Write
|
|
8
|
+
- Bash
|
|
9
|
+
- Glob
|
|
10
|
+
- Grep
|
|
11
|
+
- AskUserQuestion
|
|
12
|
+
---
|
|
13
|
+
<objective>
|
|
14
|
+
Collect phase context through structured questioning before planning begins.
|
|
15
|
+
|
|
16
|
+
**Default flow:** Load phase info -> Ask targeted questions -> Capture decisions -> Write CONTEXT.md
|
|
17
|
+
|
|
18
|
+
**Orchestrator role:** Read roadmap phase description, ask clarifying questions about scope/approach/constraints, capture all decisions and assumptions in CONTEXT.md for the planner to consume.
|
|
19
|
+
</objective>
|
|
20
|
+
|
|
21
|
+
<execution_context>
|
|
22
|
+
@~/.claude/up/workflows/discutir-fase.md
|
|
23
|
+
@~/.claude/up/references/ui-brand.md
|
|
24
|
+
</execution_context>
|
|
25
|
+
|
|
26
|
+
<context>
|
|
27
|
+
Phase: $ARGUMENTS
|
|
28
|
+
|
|
29
|
+
Discussion surfaces assumptions, clarifies gray areas, and captures decisions before planning.
|
|
30
|
+
</context>
|
|
31
|
+
|
|
32
|
+
<process>
|
|
33
|
+
Execute the discutir-fase workflow from @~/.claude/up/workflows/discutir-fase.md end-to-end.
|
|
34
|
+
Preserve all workflow gates (phase validation, questioning, decision capture, CONTEXT.md creation).
|
|
35
|
+
</process>
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:executar-fase
|
|
3
|
+
description: Executar todos os planos de uma fase com paralelizacao por ondas
|
|
4
|
+
argument-hint: "<fase> [--gaps-only]"
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Write
|
|
8
|
+
- Edit
|
|
9
|
+
- Glob
|
|
10
|
+
- Grep
|
|
11
|
+
- Bash
|
|
12
|
+
- Task
|
|
13
|
+
- AskUserQuestion
|
|
14
|
+
---
|
|
15
|
+
<objective>
|
|
16
|
+
Execute all plans in a phase using wave-based parallel execution.
|
|
17
|
+
|
|
18
|
+
Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.
|
|
19
|
+
|
|
20
|
+
Context budget: ~15% orchestrator, 100% fresh per subagent.
|
|
21
|
+
</objective>
|
|
22
|
+
|
|
23
|
+
<execution_context>
|
|
24
|
+
@~/.claude/up/workflows/executar-fase.md
|
|
25
|
+
@~/.claude/up/references/ui-brand.md
|
|
26
|
+
</execution_context>
|
|
27
|
+
|
|
28
|
+
<context>
|
|
29
|
+
Phase: $ARGUMENTS
|
|
30
|
+
|
|
31
|
+
**Flags:**
|
|
32
|
+
- `--gaps-only` -- Execute only gap closure plans (plans with `gap_closure: true` in frontmatter). Use after verificar-trabalho creates fix plans.
|
|
33
|
+
|
|
34
|
+
Context files are resolved inside the workflow and per-subagent `<files_to_read>` blocks.
|
|
35
|
+
</context>
|
|
36
|
+
|
|
37
|
+
<process>
|
|
38
|
+
Execute the executar-fase workflow from @~/.claude/up/workflows/executar-fase.md end-to-end.
|
|
39
|
+
Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing).
|
|
40
|
+
</process>
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:novo-projeto
|
|
3
|
+
description: Inicializar novo projeto com coleta de contexto e PROJECT.md
|
|
4
|
+
argument-hint: ""
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Write
|
|
8
|
+
- Bash
|
|
9
|
+
- Glob
|
|
10
|
+
- Grep
|
|
11
|
+
- Task
|
|
12
|
+
- WebFetch
|
|
13
|
+
- WebSearch
|
|
14
|
+
- AskUserQuestion
|
|
15
|
+
- mcp__context7__*
|
|
16
|
+
---
|
|
17
|
+
<objective>
|
|
18
|
+
Initialize a new project through structured context gathering and documentation.
|
|
19
|
+
|
|
20
|
+
**Default flow:** Questioning -> Research -> Requirements -> Roadmap -> PROJECT.md
|
|
21
|
+
|
|
22
|
+
**Orchestrator role:** Guide user through project discovery questions, research domain and technologies, synthesize requirements, generate phased roadmap, create PROJECT.md with all gathered context.
|
|
23
|
+
</objective>
|
|
24
|
+
|
|
25
|
+
<execution_context>
|
|
26
|
+
@~/.claude/up/workflows/novo-projeto.md
|
|
27
|
+
@~/.claude/up/references/ui-brand.md
|
|
28
|
+
</execution_context>
|
|
29
|
+
|
|
30
|
+
<context>
|
|
31
|
+
$ARGUMENTS
|
|
32
|
+
|
|
33
|
+
Project initialization collects context through interactive questioning before any planning or coding begins.
|
|
34
|
+
</context>
|
|
35
|
+
|
|
36
|
+
<process>
|
|
37
|
+
Execute the novo-projeto workflow from @~/.claude/up/workflows/novo-projeto.md end-to-end.
|
|
38
|
+
Preserve all workflow gates (questioning, research, requirements, roadmap generation, PROJECT.md creation).
|
|
39
|
+
</process>
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:pausar
|
|
3
|
+
description: Criar handoff .continue-aqui.md ao pausar trabalho
|
|
4
|
+
argument-hint: ""
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Write
|
|
8
|
+
- Bash
|
|
9
|
+
- Glob
|
|
10
|
+
- AskUserQuestion
|
|
11
|
+
---
|
|
12
|
+
<objective>
|
|
13
|
+
Create a handoff document when pausing work so the next session can resume seamlessly.
|
|
14
|
+
|
|
15
|
+
**Default flow:** Capture current state -> Document in-progress work -> Write .continue-aqui.md -> Confirm
|
|
16
|
+
|
|
17
|
+
**Orchestrator role:** Gather current task state, uncommitted changes, pending decisions, and next steps into a structured .continue-aqui.md handoff file.
|
|
18
|
+
</objective>
|
|
19
|
+
|
|
20
|
+
<execution_context>
|
|
21
|
+
@~/.claude/up/workflows/pausar.md
|
|
22
|
+
</execution_context>
|
|
23
|
+
|
|
24
|
+
<context>
|
|
25
|
+
$ARGUMENTS
|
|
26
|
+
|
|
27
|
+
Creates .continue-aqui.md in the project root with all context needed to resume work.
|
|
28
|
+
</context>
|
|
29
|
+
|
|
30
|
+
<process>
|
|
31
|
+
Execute the pausar workflow from @~/.claude/up/workflows/pausar.md end-to-end.
|
|
32
|
+
Preserve all workflow gates (state capture, change detection, handoff creation, confirmation).
|
|
33
|
+
</process>
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:planejar-fase
|
|
3
|
+
description: Planejar fase com research inline e self-check
|
|
4
|
+
argument-hint: "[fase] [--pesquisar] [--sem-pesquisa] [--auto] [--gaps]"
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Write
|
|
8
|
+
- Bash
|
|
9
|
+
- Glob
|
|
10
|
+
- Grep
|
|
11
|
+
- Task
|
|
12
|
+
- WebFetch
|
|
13
|
+
- mcp__context7__*
|
|
14
|
+
---
|
|
15
|
+
<objective>
|
|
16
|
+
Create executable phase plans (PLAN.md files) for a roadmap phase with integrated research and self-check verification.
|
|
17
|
+
|
|
18
|
+
**Default flow:** Research (if needed) -> Plan -> Verify -> Done
|
|
19
|
+
|
|
20
|
+
**Orchestrator role:** Parse arguments, validate phase, research domain (unless skipped), generate plans, verify with self-check, iterate until pass or max iterations, present results.
|
|
21
|
+
</objective>
|
|
22
|
+
|
|
23
|
+
<execution_context>
|
|
24
|
+
@~/.claude/up/workflows/planejar-fase.md
|
|
25
|
+
@~/.claude/up/references/ui-brand.md
|
|
26
|
+
</execution_context>
|
|
27
|
+
|
|
28
|
+
<context>
|
|
29
|
+
Phase number: $ARGUMENTS (optional -- auto-detects next unplanned phase if omitted)
|
|
30
|
+
|
|
31
|
+
**Flags:**
|
|
32
|
+
- `--pesquisar` -- Force re-research even if RESEARCH.md exists
|
|
33
|
+
- `--sem-pesquisa` -- Skip research, go straight to planning
|
|
34
|
+
- `--auto` -- Auto-detect and plan next unplanned phase
|
|
35
|
+
- `--gaps` -- Gap closure mode (reads VERIFICATION.md, skips research)
|
|
36
|
+
|
|
37
|
+
Normalize phase input before any directory lookups.
|
|
38
|
+
</context>
|
|
39
|
+
|
|
40
|
+
<process>
|
|
41
|
+
Execute the planejar-fase workflow from @~/.claude/up/workflows/planejar-fase.md end-to-end.
|
|
42
|
+
Preserve all workflow gates (validation, research, planning, verification loop, routing).
|
|
43
|
+
</process>
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:progresso
|
|
3
|
+
description: Status do projeto e roteamento para proxima acao
|
|
4
|
+
argument-hint: ""
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Bash
|
|
8
|
+
- Glob
|
|
9
|
+
- Grep
|
|
10
|
+
---
|
|
11
|
+
<objective>
|
|
12
|
+
Display current project status and route to the next recommended action.
|
|
13
|
+
|
|
14
|
+
**Default flow:** Read STATE.md -> Analyze progress -> Show status dashboard -> Recommend next action
|
|
15
|
+
|
|
16
|
+
**Orchestrator role:** Read project state, calculate completion percentages, identify current phase and blockers, present formatted status, suggest next UP command to run.
|
|
17
|
+
</objective>
|
|
18
|
+
|
|
19
|
+
<execution_context>
|
|
20
|
+
@~/.claude/up/workflows/progresso.md
|
|
21
|
+
@~/.claude/up/references/ui-brand.md
|
|
22
|
+
</execution_context>
|
|
23
|
+
|
|
24
|
+
<context>
|
|
25
|
+
$ARGUMENTS
|
|
26
|
+
|
|
27
|
+
Reads project state to provide a clear picture of where things stand and what to do next.
|
|
28
|
+
</context>
|
|
29
|
+
|
|
30
|
+
<process>
|
|
31
|
+
Execute the progresso workflow from @~/.claude/up/workflows/progresso.md end-to-end.
|
|
32
|
+
Preserve all workflow gates (state reading, progress calculation, status display, action routing).
|
|
33
|
+
</process>
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:rapido
|
|
3
|
+
description: Tarefa rapida com garantias UP (commits atomicos, rastreamento)
|
|
4
|
+
argument-hint: "[descricao]"
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Write
|
|
8
|
+
- Edit
|
|
9
|
+
- Glob
|
|
10
|
+
- Grep
|
|
11
|
+
- Bash
|
|
12
|
+
- Task
|
|
13
|
+
- AskUserQuestion
|
|
14
|
+
---
|
|
15
|
+
<objective>
|
|
16
|
+
Execute small, ad-hoc tasks with UP guarantees (atomic commits, STATE.md tracking).
|
|
17
|
+
|
|
18
|
+
Quick mode is the same system with a shorter path:
|
|
19
|
+
- Plans and executes in a streamlined flow
|
|
20
|
+
- Quick tasks live in `.plano/rapido/` separate from planned phases
|
|
21
|
+
- Updates STATE.md "Tarefas Rapidas" table (NOT ROADMAP.md)
|
|
22
|
+
|
|
23
|
+
**Default:** Skips research, discussion, plan-checker, verifier. Use when you know exactly what to do.
|
|
24
|
+
</objective>
|
|
25
|
+
|
|
26
|
+
<execution_context>
|
|
27
|
+
@~/.claude/up/workflows/rapido.md
|
|
28
|
+
@~/.claude/up/references/ui-brand.md
|
|
29
|
+
</execution_context>
|
|
30
|
+
|
|
31
|
+
<context>
|
|
32
|
+
$ARGUMENTS
|
|
33
|
+
|
|
34
|
+
Quick tasks get UP guarantees without full phase ceremony.
|
|
35
|
+
</context>
|
|
36
|
+
|
|
37
|
+
<process>
|
|
38
|
+
Execute the rapido workflow from @~/.claude/up/workflows/rapido.md end-to-end.
|
|
39
|
+
Preserve all workflow gates (validation, task description, planning, execution, state updates, commits).
|
|
40
|
+
</process>
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:remover-fase
|
|
3
|
+
description: Remover fase futura e renumerar subsequentes
|
|
4
|
+
argument-hint: "<numero>"
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Write
|
|
8
|
+
- Edit
|
|
9
|
+
- Bash
|
|
10
|
+
- Glob
|
|
11
|
+
- AskUserQuestion
|
|
12
|
+
---
|
|
13
|
+
<objective>
|
|
14
|
+
Remove a future phase from the roadmap and renumber all subsequent phases.
|
|
15
|
+
|
|
16
|
+
**Flow:** Validate future phase -> Confirm with user -> Call `up-tools.cjs phase remove` -> Present result
|
|
17
|
+
</objective>
|
|
18
|
+
|
|
19
|
+
<execution_context>
|
|
20
|
+
@~/.claude/up/workflows/remover-fase.md
|
|
21
|
+
</execution_context>
|
|
22
|
+
|
|
23
|
+
<context>
|
|
24
|
+
Phase number: $ARGUMENTS
|
|
25
|
+
|
|
26
|
+
Only future (not started) phases can be removed. Active or completed phases are protected.
|
|
27
|
+
</context>
|
|
28
|
+
|
|
29
|
+
<process>
|
|
30
|
+
1. Validate that the specified phase number exists and is a future phase (not active or completed).
|
|
31
|
+
2. Confirm removal with the user via AskUserQuestion.
|
|
32
|
+
3. Call `up-tools.cjs phase remove` with the phase number.
|
|
33
|
+
4. Present the updated roadmap showing renumbered phases.
|
|
34
|
+
</process>
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:retomar
|
|
3
|
+
description: Restaurar contexto da sessao anterior
|
|
4
|
+
argument-hint: ""
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Write
|
|
8
|
+
- Bash
|
|
9
|
+
- Glob
|
|
10
|
+
- Grep
|
|
11
|
+
- AskUserQuestion
|
|
12
|
+
---
|
|
13
|
+
<objective>
|
|
14
|
+
Restore context from the previous session and resume work where it left off.
|
|
15
|
+
|
|
16
|
+
**Default flow:** Find .continue-aqui.md -> Load context -> Validate state -> Present summary -> Resume
|
|
17
|
+
|
|
18
|
+
**Orchestrator role:** Locate and read .continue-aqui.md handoff file, validate that project state matches expectations, present summary of where things stand, and route to the appropriate next action.
|
|
19
|
+
</objective>
|
|
20
|
+
|
|
21
|
+
<execution_context>
|
|
22
|
+
@~/.claude/up/workflows/retomar.md
|
|
23
|
+
@~/.claude/up/references/ui-brand.md
|
|
24
|
+
</execution_context>
|
|
25
|
+
|
|
26
|
+
<context>
|
|
27
|
+
$ARGUMENTS
|
|
28
|
+
|
|
29
|
+
Reads .continue-aqui.md from the project root to restore previous session context.
|
|
30
|
+
</context>
|
|
31
|
+
|
|
32
|
+
<process>
|
|
33
|
+
Execute the retomar workflow from @~/.claude/up/workflows/retomar.md end-to-end.
|
|
34
|
+
Preserve all workflow gates (handoff detection, context loading, state validation, summary, routing).
|
|
35
|
+
</process>
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: up:verificar-trabalho
|
|
3
|
+
description: Validar features atraves de UAT conversacional
|
|
4
|
+
argument-hint: "[fase]"
|
|
5
|
+
allowed-tools:
|
|
6
|
+
- Read
|
|
7
|
+
- Write
|
|
8
|
+
- Bash
|
|
9
|
+
- Glob
|
|
10
|
+
- Grep
|
|
11
|
+
- AskUserQuestion
|
|
12
|
+
---
|
|
13
|
+
<objective>
|
|
14
|
+
Validate implemented features through conversational UAT (User Acceptance Testing).
|
|
15
|
+
|
|
16
|
+
**Default flow:** Load phase plans -> Test each feature -> Collect feedback -> Generate VERIFICATION.md -> Route to fix or approve
|
|
17
|
+
|
|
18
|
+
**Orchestrator role:** Read completed plans, run tests and checks, engage user in conversational validation, document results in VERIFICATION.md, create gap closure plans if needed.
|
|
19
|
+
</objective>
|
|
20
|
+
|
|
21
|
+
<execution_context>
|
|
22
|
+
@~/.claude/up/workflows/verificar-trabalho.md
|
|
23
|
+
@~/.claude/up/references/ui-brand.md
|
|
24
|
+
</execution_context>
|
|
25
|
+
|
|
26
|
+
<context>
|
|
27
|
+
Phase: $ARGUMENTS (optional -- defaults to current active phase)
|
|
28
|
+
|
|
29
|
+
Verification validates that implemented features match the planned requirements.
|
|
30
|
+
</context>
|
|
31
|
+
|
|
32
|
+
<process>
|
|
33
|
+
Execute the verificar-trabalho workflow from @~/.claude/up/workflows/verificar-trabalho.md end-to-end.
|
|
34
|
+
Preserve all workflow gates (plan loading, testing, user validation, VERIFICATION.md creation, routing).
|
|
35
|
+
</process>
|
package/package.json
ADDED
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "up-cc",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"description": "Simplified spec-driven development for Claude Code, Gemini and OpenCode.",
|
|
5
|
+
"bin": {
|
|
6
|
+
"up-cc": "bin/install.js"
|
|
7
|
+
},
|
|
8
|
+
"files": [
|
|
9
|
+
"bin",
|
|
10
|
+
"agents",
|
|
11
|
+
"commands",
|
|
12
|
+
"workflows",
|
|
13
|
+
"templates",
|
|
14
|
+
"references"
|
|
15
|
+
],
|
|
16
|
+
"keywords": [
|
|
17
|
+
"claude",
|
|
18
|
+
"claude-code",
|
|
19
|
+
"gemini",
|
|
20
|
+
"gemini-cli",
|
|
21
|
+
"opencode",
|
|
22
|
+
"ai",
|
|
23
|
+
"spec-driven-development",
|
|
24
|
+
"meta-prompting",
|
|
25
|
+
"context-engineering"
|
|
26
|
+
],
|
|
27
|
+
"author": "",
|
|
28
|
+
"license": "MIT",
|
|
29
|
+
"engines": {
|
|
30
|
+
"node": ">=16.7.0"
|
|
31
|
+
}
|
|
32
|
+
}
|