@claude-pw/framework 0.11.0 → 0.11.1
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/README.es.md +4 -2
- package/README.ja.md +4 -2
- package/README.md +7 -2
- package/README.pt-br.md +4 -2
- package/README.zh-cn.md +4 -2
- package/package.json +1 -1
package/README.es.md
CHANGED
|
@@ -54,12 +54,13 @@ npx @claude-pw/framework --update
|
|
|
54
54
|
## Cómo funciona
|
|
55
55
|
|
|
56
56
|
```
|
|
57
|
-
/cpw-startup → /cpw-
|
|
57
|
+
/cpw-startup → /cpw-next-step (repetir) → plan completo → /cpw-startup (nuevo ciclo)
|
|
58
58
|
```
|
|
59
59
|
|
|
60
|
-
1. **`/cpw-startup`** te entrevista, escanea código existente (si hay), y genera un plan con fases, pasos y docs de arquitectura
|
|
60
|
+
1. **`/cpw-startup`** te entrevista, escanea código existente (si hay), y genera un plan con fases, pasos y docs de arquitectura. En ciclos posteriores, carga el contexto previo y agrega nuevas fases.
|
|
61
61
|
2. **`/cpw-discuss`** identifica zonas grises y captura tus preferencias antes de construir (opcional, por fase)
|
|
62
62
|
3. **`/cpw-next-step`** ejecuta un pipeline adaptativo por paso — luego cierra, commitea y avanza automáticamente
|
|
63
|
+
4. Cuando todas las fases se completan, **`/cpw-cleanup --complete`** se ejecuta automáticamente: genera un resumen del plan, revisa docs, archiva todas las fases, resetea el estado de ejecución y deja el proyecto listo para el siguiente `/cpw-startup`
|
|
63
64
|
|
|
64
65
|
Cada paso pasa por:
|
|
65
66
|
|
|
@@ -137,6 +138,7 @@ Issue capturado. ¿Arreglar ahora? (sí/no)
|
|
|
137
138
|
| `/cpw-todos` | Captura ideas para después o revisa todos pendientes |
|
|
138
139
|
| `/cpw-reflect` | Revisa correcciones capturadas, convierte en learnings (`--scan-history`, `--dedupe`) |
|
|
139
140
|
| `/cpw-impact` | Analiza impacto de decisiones en todo el plan |
|
|
141
|
+
| `/cpw-cleanup` | Archiva fases completadas y limpia estado (`--complete` para reset completo del plan) |
|
|
140
142
|
| `/cpw-update` | Actualización inteligente del framework — diff, merge de conflictos, preserva customizaciones |
|
|
141
143
|
|
|
142
144
|
## Configuración
|
package/README.ja.md
CHANGED
|
@@ -54,12 +54,13 @@ npx @claude-pw/framework --update
|
|
|
54
54
|
## 仕組み
|
|
55
55
|
|
|
56
56
|
```
|
|
57
|
-
/cpw-startup → /cpw-
|
|
57
|
+
/cpw-startup → /cpw-next-step(繰り返し)→ 計画完了 → /cpw-startup(新サイクル)
|
|
58
58
|
```
|
|
59
59
|
|
|
60
|
-
1. **`/cpw-startup`**
|
|
60
|
+
1. **`/cpw-startup`** インタビューを行い、既存コード(あれば)をスキャンし、フェーズ・ステップ・アーキテクチャドキュメントを含む計画を生成。後続サイクルでは、以前のコンテキストを読み込み、新しいフェーズを追加。
|
|
61
61
|
2. **`/cpw-discuss`** グレーゾーンを特定し、ビルド前にあなたの好みを把握(任意、フェーズごと)
|
|
62
62
|
3. **`/cpw-next-step`** ステップごとに適応型パイプラインを実行 — 完了後、自動的にクローズ・コミット・次へ進行
|
|
63
|
+
4. 全フェーズ完了時、**`/cpw-cleanup --complete`** が自動実行:計画サマリー生成、ドキュメントレビュー、全フェーズアーカイブ、実行状態リセット、次の `/cpw-startup` に備える
|
|
63
64
|
|
|
64
65
|
各ステップは以下を経由します:
|
|
65
66
|
|
|
@@ -137,6 +138,7 @@ Issue captured. Fix now? (yes/no)
|
|
|
137
138
|
| `/cpw-todos` | アイデアの記録または保留中の TODO の確認 |
|
|
138
139
|
| `/cpw-reflect` | キャプチャした修正をレビューし、学習に変換(`--scan-history`, `--dedupe`) |
|
|
139
140
|
| `/cpw-impact` | 計画全体にわたる意思決定の影響分析 |
|
|
141
|
+
| `/cpw-cleanup` | 完了フェーズのアーカイブと状態クリーンアップ(`--complete` で計画全体リセット) |
|
|
140
142
|
| `/cpw-update` | スマートフレームワーク更新 — 差分、コンフリクトマージ、カスタマイズ保持 |
|
|
141
143
|
|
|
142
144
|
## 設定
|
package/README.md
CHANGED
|
@@ -54,12 +54,13 @@ npx @claude-pw/framework --update
|
|
|
54
54
|
## How it works
|
|
55
55
|
|
|
56
56
|
```
|
|
57
|
-
/cpw-startup → /cpw-
|
|
57
|
+
/cpw-startup → /cpw-next-step (repeat) → plan complete → /cpw-startup (new cycle)
|
|
58
58
|
```
|
|
59
59
|
|
|
60
|
-
1. **`/cpw-startup`** interviews you, scans existing code (if any), and generates a plan with phases, steps, and architecture docs
|
|
60
|
+
1. **`/cpw-startup`** interviews you, scans existing code (if any), and generates a plan with phases, steps, and architecture docs. On subsequent cycles, loads prior context and appends new phases.
|
|
61
61
|
2. **`/cpw-discuss`** identifies gray areas and captures your preferences before building (optional, per phase)
|
|
62
62
|
3. **`/cpw-next-step`** runs an adaptive pipeline per step — then closes, commits, and advances automatically
|
|
63
|
+
4. When all phases complete, **`/cpw-cleanup --complete`** runs automatically: generates a plan summary, reviews docs for drift, archives all phase files, resets execution state, and leaves the project ready for the next `/cpw-startup`
|
|
63
64
|
|
|
64
65
|
Every step goes through:
|
|
65
66
|
|
|
@@ -137,6 +138,7 @@ Issue captured. Fix now? (yes/no)
|
|
|
137
138
|
| `/cpw-todos` | Capture ideas for later or review pending todos |
|
|
138
139
|
| `/cpw-reflect` | Review captured corrections, convert to learnings (`--scan-history`, `--dedupe`) |
|
|
139
140
|
| `/cpw-impact` | Analyze decision impact across the entire plan |
|
|
141
|
+
| `/cpw-cleanup` | Archive completed phases and clean state (`--complete` for full plan reset) |
|
|
140
142
|
| `/cpw-update` | Smart framework update — diff, merge conflicts, preserve customizations |
|
|
141
143
|
|
|
142
144
|
## Configuration
|
|
@@ -152,6 +154,9 @@ Issue captured. Fix now? (yes/no)
|
|
|
152
154
|
| `gitStrategy` | `trunk-based` / `feature-branch` / `gitflow` | `trunk-based` | `trunk-based` = push to main. `feature-branch` = branch per phase, PR to merge. `gitflow` = develop + feature branches. |
|
|
153
155
|
| `commitPlanning` | `true` / `false` | `false` | Track `.planning/` in git (for teams) |
|
|
154
156
|
| `autoReflect` | `off` / `remind` / `auto` | `remind` | Auto-process learnings at session end or CLOSE stage |
|
|
157
|
+
| `cleanupPolicy` | `{...}` | see below | Retention limits for mid-plan cleanup |
|
|
158
|
+
|
|
159
|
+
`cleanupPolicy` defaults: `archiveCompletedPhases: true`, `keepAppliedLearnings: 20`, `keepResolvedDebug: 5`, `keepQuickLogDone: 10`
|
|
155
160
|
|
|
156
161
|
## What goes in git
|
|
157
162
|
|
package/README.pt-br.md
CHANGED
|
@@ -54,12 +54,13 @@ npx @claude-pw/framework --update
|
|
|
54
54
|
## Como funciona
|
|
55
55
|
|
|
56
56
|
```
|
|
57
|
-
/cpw-startup → /cpw-
|
|
57
|
+
/cpw-startup → /cpw-next-step (repetir) → plano completo → /cpw-startup (novo ciclo)
|
|
58
58
|
```
|
|
59
59
|
|
|
60
|
-
1. **`/cpw-startup`** entrevista você, analisa o código existente (se houver) e gera um plano com fases, etapas e documentos de arquitetura
|
|
60
|
+
1. **`/cpw-startup`** entrevista você, analisa o código existente (se houver) e gera um plano com fases, etapas e documentos de arquitetura. Em ciclos posteriores, carrega o contexto anterior e adiciona novas fases.
|
|
61
61
|
2. **`/cpw-discuss`** identifica áreas cinzentas e captura suas preferências antes de construir (opcional, por fase)
|
|
62
62
|
3. **`/cpw-next-step`** executa um pipeline adaptativo por etapa — então fecha, commita e avança automaticamente
|
|
63
|
+
4. Quando todas as fases completam, **`/cpw-cleanup --complete`** executa automaticamente: gera resumo do plano, revisa docs, arquiva todas as fases, reseta estado de execução e deixa o projeto pronto para o próximo `/cpw-startup`
|
|
63
64
|
|
|
64
65
|
Cada etapa passa por:
|
|
65
66
|
|
|
@@ -137,6 +138,7 @@ Issue captured. Fix now? (yes/no)
|
|
|
137
138
|
| `/cpw-todos` | Capturar ideias para depois ou revisar todos pendentes |
|
|
138
139
|
| `/cpw-reflect` | Revisar correções capturadas, converter em aprendizados (`--scan-history`, `--dedupe`) |
|
|
139
140
|
| `/cpw-impact` | Analisar impacto de decisões em todo o plano |
|
|
141
|
+
| `/cpw-cleanup` | Arquivar fases completadas e limpar estado (`--complete` para reset completo do plano) |
|
|
140
142
|
| `/cpw-update` | Atualização inteligente do framework — diff, merge de conflitos, preserva customizações |
|
|
141
143
|
|
|
142
144
|
## Configuração
|
package/README.zh-cn.md
CHANGED
|
@@ -54,12 +54,13 @@ npx @claude-pw/framework --update
|
|
|
54
54
|
## 工作原理
|
|
55
55
|
|
|
56
56
|
```
|
|
57
|
-
/cpw-startup → /cpw-
|
|
57
|
+
/cpw-startup → /cpw-next-step(重复)→ 计划完成 → /cpw-startup(新周期)
|
|
58
58
|
```
|
|
59
59
|
|
|
60
|
-
1. **`/cpw-startup`**
|
|
60
|
+
1. **`/cpw-startup`** 对你进行访谈,扫描现有代码(如果有),生成包含阶段、步骤和架构文档的计划。后续周期中,加载之前的上下文并追加新阶段。
|
|
61
61
|
2. **`/cpw-discuss`** 识别灰色地带,在构建前捕获你的偏好(可选,按阶段)
|
|
62
62
|
3. **`/cpw-next-step`** 按步骤运行自适应流水线——然后自动关闭、提交并推进
|
|
63
|
+
4. 当所有阶段完成时,**`/cpw-cleanup --complete`** 自动运行:生成计划摘要、审查文档、归档所有阶段文件、重置执行状态,为下一个 `/cpw-startup` 做好准备
|
|
63
64
|
|
|
64
65
|
每个步骤经过:
|
|
65
66
|
|
|
@@ -137,6 +138,7 @@ UAT 演练:
|
|
|
137
138
|
| `/cpw-todos` | 捕获想法或查看待办事项 |
|
|
138
139
|
| `/cpw-reflect` | 审查捕获的修正,转化为学习成果(`--scan-history`、`--dedupe`) |
|
|
139
140
|
| `/cpw-impact` | 分析决策对整个计划的影响 |
|
|
141
|
+
| `/cpw-cleanup` | 归档已完成阶段并清理状态(`--complete` 用于完整计划重置) |
|
|
140
142
|
| `/cpw-update` | 智能框架更新 — 差异对比、冲突合并、保留自定义 |
|
|
141
143
|
|
|
142
144
|
## 配置
|
package/package.json
CHANGED