no-mistakes(document): Sync onboard documentation
This commit is contained in:
Jeremy McSpadden
committed by
Codesmith
Codesmith
parent
b006b1a23e
commit
a3cca0704d
@@ -47,13 +47,14 @@ The installer prompts for your runtime (Claude Code, OpenCode, Antigravity CLI,
|
||||
|
||||
On another runtime or without Node.js? See [Install on your runtime](docs/how-to/install-on-your-runtime.md).
|
||||
|
||||
Once installed, start your first project:
|
||||
Once installed, start a new project or onboard an existing repo:
|
||||
|
||||
```bash
|
||||
/gsd-new-project
|
||||
/gsd-new-project # greenfield project
|
||||
/gsd-onboard # existing codebase
|
||||
```
|
||||
|
||||
New here? Follow [Your first project](docs/tutorials/your-first-project.md) for a guided walkthrough from install to first shipped phase.
|
||||
New here? Follow [Your first project](docs/tutorials/your-first-project.md) for a guided walkthrough from install to first shipped phase, or [Onboarding an existing codebase](docs/tutorials/onboarding-an-existing-codebase.md) for brownfield setup.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ Parse the first token of $ARGUMENTS:
|
||||
Check for .planning/STATE.md - loads context if project already initialized
|
||||
|
||||
**This command can run:**
|
||||
- Before /gsd:new-project (brownfield codebases) - creates codebase map first
|
||||
- Via /gsd:onboard for first-time brownfield setup - creates codebase map first
|
||||
- After /gsd:new-project (greenfield codebases) - updates codebase map as code evolves
|
||||
- Anytime to refresh codebase understanding
|
||||
</context>
|
||||
@@ -51,7 +51,7 @@ Check for .planning/STATE.md - loads context if project already initialized
|
||||
**Use map-codebase for:**
|
||||
- Brownfield projects before initialization (understand existing code first)
|
||||
- Refreshing codebase map after significant changes
|
||||
- Onboarding to an unfamiliar codebase
|
||||
- Refreshing or deepening an onboarded codebase map
|
||||
- Before major refactoring (understand current state)
|
||||
- When STATE.md references outdated codebase info
|
||||
|
||||
@@ -71,7 +71,7 @@ Check for .planning/STATE.md - loads context if project already initialized
|
||||
4. Wait for agents to complete, collect confirmations (NOT document contents)
|
||||
5. Verify all 7 documents exist with line counts
|
||||
6. Commit codebase map
|
||||
7. Offer next steps (typically: /gsd:new-project or /gsd:plan-phase)
|
||||
7. Offer next steps (typically: /gsd:onboard, /gsd:new-project, or /gsd:plan-phase)
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
|
||||
@@ -421,13 +421,14 @@ node gsd-tools.cjs scaffold phase-dir --phase N --name "phase name"
|
||||
|
||||
## Init Commands (Compound Context Loading)
|
||||
|
||||
Load all context needed for a specific workflow in one call. Returns JSON with project info, config, state, and workflow-specific data.
|
||||
Load all context needed for a specific workflow in one call. Returns JSON with project info, config, state, and workflow-specific data. `init onboard` reports brownfield signals, planning-doc candidates, codebase-map completeness, partial planning state, and onboarding summary status for `/gsd-onboard`.
|
||||
|
||||
```bash
|
||||
node gsd-tools.cjs init execute-phase <phase>
|
||||
node gsd-tools.cjs init plan-phase <phase>
|
||||
node gsd-tools.cjs init new-project
|
||||
node gsd-tools.cjs init new-milestone
|
||||
node gsd-tools.cjs init onboard
|
||||
node gsd-tools.cjs init quick <description>
|
||||
node gsd-tools.cjs init resume
|
||||
node gsd-tools.cjs init verify-work <phase>
|
||||
|
||||
@@ -1202,7 +1202,7 @@ gsd capability remove my-cap --scope project # Turn the installed overl
|
||||
|
||||
### `/gsd-map-codebase`
|
||||
|
||||
Analyze existing codebase with parallel mapper agents. Use `--fast` for a quick single-agent scan, or `--query` to search existing intel.
|
||||
Analyze existing codebase with parallel mapper agents. Use `--fast` for a quick single-agent scan, or `--query` to search existing intel. First-time brownfield setup should usually start with `/gsd-onboard`, which hands off to this command when a map is missing.
|
||||
|
||||
| Argument | Required | Description |
|
||||
|----------|----------|-------------|
|
||||
|
||||
@@ -38,6 +38,7 @@
|
||||
- [Model Profiles](#26-model-profiles)
|
||||
- [Brownfield Features](#brownfield-features)
|
||||
- [Codebase Mapping](#27-codebase-mapping)
|
||||
- [Existing Codebase Onboarding](#27b-existing-codebase-onboarding)
|
||||
- [Utility Features](#utility-features)
|
||||
- [Debug System](#28-debug-system)
|
||||
- [Todo Management](#29-todo-management)
|
||||
@@ -789,7 +790,7 @@
|
||||
|
||||
**Command:** `/gsd-map-codebase [area]`
|
||||
|
||||
**Purpose:** Analyze an existing codebase before starting a new project, so GSD understands what exists.
|
||||
**Purpose:** Analyze an existing codebase before starting a new project or as the mapping handoff from `/gsd-onboard`, so GSD understands what exists.
|
||||
|
||||
**Requirements:**
|
||||
- REQ-MAP-01: System MUST spawn parallel mapper agents for each analysis area
|
||||
@@ -817,6 +818,27 @@ only the subtrees the phase actually changed. Each produced document carries
|
||||
`last_mapped_commit` in its YAML frontmatter so drift can be measured
|
||||
against the mapping point, not HEAD.
|
||||
|
||||
### 27b. Existing Codebase Onboarding
|
||||
|
||||
**Command:** `/gsd-onboard [--fast] [--text]`
|
||||
|
||||
**Purpose:** Guide first-time setup for an existing repository by checking brownfield state, routing through codebase mapping and docs ingest, then handing off to project initialization without silently overwriting planning artifacts.
|
||||
|
||||
**Requirements:**
|
||||
- REQ-ONBOARD-01: System MUST detect existing code, package manifests, planning documents, partial `.planning/` state, and complete or missing codebase-map files.
|
||||
- REQ-ONBOARD-02: System MUST hand off to `/gsd-map-codebase` or `/gsd-map-codebase --fast` when brownfield code lacks a complete `.planning/codebase/` map.
|
||||
- REQ-ONBOARD-03: System MUST offer `/gsd-ingest-docs` before `/gsd-new-project` when ADR/PRD/SPEC/RFC candidates exist and no project exists.
|
||||
- REQ-ONBOARD-04: System MUST refuse to report onboarding complete until `PROJECT.md`, `REQUIREMENTS.md`, `ROADMAP.md`, and `STATE.md` all exist.
|
||||
- REQ-ONBOARD-05: System MUST create or confirm `.planning/onboarding/SUMMARY.md` only after project setup exists.
|
||||
- REQ-ONBOARD-06: System MUST support `--text` for numbered plain-text gates on runtimes without interactive menus.
|
||||
|
||||
**Produces:**
|
||||
| Artifact | Description |
|
||||
|----------|-------------|
|
||||
| `.planning/codebase/` | Codebase map produced by the `/gsd-map-codebase` handoff |
|
||||
| `.planning/PROJECT.md`, `REQUIREMENTS.md`, `ROADMAP.md`, `STATE.md` | Planning setup produced by `/gsd-new-project` or `/gsd-ingest-docs` |
|
||||
| `.planning/onboarding/SUMMARY.md` | Onboarding status, artifact index, and next-command summary |
|
||||
|
||||
### 27a. Post-Execute Codebase Drift Detection
|
||||
|
||||
**Introduced by:** #2003
|
||||
|
||||
@@ -79,7 +79,7 @@ The core GSD loop is: **discuss → plan → execute → verify → ship**, repe
|
||||
|
||||
See [Your first project](tutorials/your-first-project.md).
|
||||
|
||||
For onboarding an existing codebase before starting a new milestone, see [Onboarding an existing codebase](tutorials/onboarding-an-existing-codebase.md).
|
||||
For onboarding an existing codebase before starting a new milestone, run `/gsd-onboard` or see [Onboarding an existing codebase](tutorials/onboarding-an-existing-codebase.md).
|
||||
|
||||
**Relevant flags at a glance:**
|
||||
|
||||
@@ -536,11 +536,13 @@ claude --dangerously-skip-permissions
|
||||
### Existing Codebase
|
||||
|
||||
```bash
|
||||
/gsd-map-codebase # Analyse what exists (parallel agents)
|
||||
/gsd-new-project # Questions focus on what you're ADDING
|
||||
/gsd-onboard # Safely map, ingest docs, and initialize planning
|
||||
# Follow the printed top-level handoff commands, then rerun /gsd-onboard
|
||||
# (normal phase workflow from here)
|
||||
```
|
||||
|
||||
`/gsd-onboard` routes through `/gsd-map-codebase`, `/gsd-ingest-docs`, and `/gsd-new-project` without nesting interactive workflows or overwriting existing planning files silently.
|
||||
|
||||
**Post-execute drift detection (#2003).** After every `/gsd-execute-phase`, GSD checks whether the phase introduced enough structural change to make `.planning/codebase/STRUCTURE.md` stale. Flip the behavior with:
|
||||
|
||||
```bash
|
||||
@@ -986,7 +988,8 @@ To disable parallel execution entirely: `/gsd-settings` → set `parallelization
|
||||
themes/
|
||||
default.css # Shared CSS variables for all sketches
|
||||
MANIFEST.md # Index of all sketches with winners
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase)
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase or /gsd-onboard)
|
||||
onboarding/ # Brownfield onboarding summary (from /gsd-onboard)
|
||||
phases/
|
||||
XX-phase-name/
|
||||
XX-YY-PLAN.md # Atomic execution plans
|
||||
|
||||
@@ -51,6 +51,25 @@ v1.40 では、最初のステージエントリーポイントとして6つの
|
||||
|
||||
---
|
||||
|
||||
### `/gsd-onboard`
|
||||
|
||||
既存コードベースの初回 GSD オンボーディングを案内します。リポジトリ状態を確認し、コードベースマッピング、任意のドキュメント取り込み、プロジェクト初期化へ安全にハンドオフし、計画が揃った後にオンボーディング summary を作成します。
|
||||
|
||||
| フラグ | 説明 |
|
||||
|------|-------------|
|
||||
| `--fast` | 軽量な `/gsd-map-codebase --fast` マッピングハンドオフを優先 |
|
||||
| `--text` | TUI メニューではなく番号付きプレーンテキストのゲートを使用 |
|
||||
|
||||
**前提条件:** 既存リポジトリまたは計画ドキュメント。空のグリーンフィールドプロジェクトには `/gsd-new-project` を使用します。
|
||||
**生成物:** map-codebase による `.planning/codebase/`、new-project または ingest-docs による `.planning/`、セットアップ後の `.planning/onboarding/SUMMARY.md`。
|
||||
|
||||
```bash
|
||||
/gsd-onboard # ガイド付き brownfield オンボーディング
|
||||
/gsd-onboard --fast # 先に軽量コードベースマッピングを使用
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### `/gsd-workspace`
|
||||
|
||||
GSD ワークスペースを管理 — リポジトリコピーと独立した `.planning/` ディレクトリを持つ隔離されたワークスペース環境を作成、一覧表示、または削除します。
|
||||
|
||||
@@ -38,6 +38,7 @@
|
||||
- [モデルプロファイル](#26-モデルプロファイル)
|
||||
- [ブラウンフィールド機能](#ブラウンフィールド機能)
|
||||
- [コードベースマッピング](#27-コードベースマッピング)
|
||||
- [既存コードベースオンボーディング](#27b-既存コードベースオンボーディング)
|
||||
- [ユーティリティ機能](#ユーティリティ機能)
|
||||
- [デバッグシステム](#28-デバッグシステム)
|
||||
- [Todo 管理](#29-todo-管理)
|
||||
@@ -781,7 +782,7 @@
|
||||
|
||||
**コマンド:** `/gsd-map-codebase [area]`
|
||||
|
||||
**目的:** 新しいプロジェクトを開始する前に既存のコードベースを分析し、GSD が既存の構成を理解できるようにします。
|
||||
**目的:** 新しいプロジェクトを開始する前、または `/gsd-onboard` からのマッピングハンドオフとして既存のコードベースを分析し、GSD が既存の構成を理解できるようにします。
|
||||
|
||||
**要件:**
|
||||
- REQ-MAP-01: システムは各分析領域に対して並列マッパーエージェントを起動しなければならない
|
||||
@@ -805,6 +806,19 @@
|
||||
`--paths <p1,p2,...>` スコープヒントを受け付けます。指定した場合、ツリー全体をスキャンする代わりに、リストされたリポジトリ相対プレフィックスに探索を制限します。
|
||||
これはフェーズが実際に変更したサブツリーのみを更新するために、実行後コードベースドリフトゲートが使用するパスウェイです。各生成ドキュメントはその YAML フロントマターに `last_mapped_commit` を持ち、ドリフトを HEAD ではなくマッピング時点と照らし合わせて計測できます。
|
||||
|
||||
### 27b. 既存コードベースオンボーディング
|
||||
|
||||
**コマンド:** `/gsd-onboard [--fast] [--text]`
|
||||
|
||||
**目的:** 既存リポジトリの初回セットアップを案内し、brownfield 状態を確認してコードベースマッピング、docs 取り込み、プロジェクト初期化へ安全にハンドオフします。
|
||||
|
||||
**要件:**
|
||||
- REQ-ONBOARD-01: 既存コード、package manifest、計画ドキュメント、部分的な `.planning/`、コードベースマップの不足を検出する。
|
||||
- REQ-ONBOARD-02: 完全な `.planning/codebase/` がない brownfield では `/gsd-map-codebase` または `/gsd-map-codebase --fast` へハンドオフする。
|
||||
- REQ-ONBOARD-03: ADR/PRD/SPEC/RFC 候補があり project がない場合、`/gsd-new-project` の前に `/gsd-ingest-docs` を提示する。
|
||||
- REQ-ONBOARD-04: `PROJECT.md`、`REQUIREMENTS.md`、`ROADMAP.md`、`STATE.md` が揃うまで完了扱いにしない。
|
||||
- REQ-ONBOARD-05: project setup 後にのみ `.planning/onboarding/SUMMARY.md` を作成または確認する。
|
||||
|
||||
### 27a. 実行後コードベースドリフト検出
|
||||
|
||||
**導入:** #2003
|
||||
|
||||
@@ -78,6 +78,7 @@
|
||||
| コマンド | 役割 | ソース |
|
||||
|----------|------|--------|
|
||||
| `/gsd-new-project` | 深いコンテキスト収集と PROJECT.md で新しいプロジェクトを初期化。 | [commands/gsd/new-project.md](../../commands/gsd/new-project.md) |
|
||||
| `/gsd-onboard` | 既存コードベースをマッピング、ドキュメント取り込み、プロジェクト設定、onboarding summary へ案内。 | [commands/gsd/onboard.md](../../commands/gsd/onboard.md) |
|
||||
| `/gsd-workspace` | GSD ワークスペースを管理 — 独立したワークスペース環境を作成（`--new`）、一覧表示（`--list`）、削除（`--remove`）。 | [commands/gsd/workspace.md](../../commands/gsd/workspace.md) |
|
||||
| `/gsd-discuss-phase` | 計画前にアダプティブな質問でフェーズコンテキストを収集。 | [commands/gsd/discuss-phase.md](../../commands/gsd/discuss-phase.md) |
|
||||
| `/gsd-mvp-phase` | フェーズを垂直 MVP スライスとして計画 — ユーザーストーリー、SPIDR 分割、その後 plan-phase。 | [commands/gsd/mvp-phase.md](../../commands/gsd/mvp-phase.md) |
|
||||
@@ -218,6 +219,7 @@
|
||||
| `milestone-summary.md` | マイルストーンサマリー合成 — マイルストーンアーティファクトからオンボーディングとレビューアーティファクトを作成。 | `/gsd-milestone-summary` |
|
||||
| `new-milestone.md` | 新しいマイルストーンサイクルを開始 — プロジェクトコンテキストを読み込み、目標を収集して PROJECT.md/STATE.md を更新。 | `/gsd-new-milestone` |
|
||||
| `new-project.md` | 統合新プロジェクトフロー — 質問、調査（任意）、要件、ロードマップ。 | `/gsd-new-project` |
|
||||
| `onboard.md` | Brownfield onboarding orchestration — コードベースをマップし、docs を取り込み、planning を初期化し、次のステップを要約。 | `/gsd-onboard` |
|
||||
| `new-workspace.md` | リポジトリのワークツリー/クローンと独立した `.planning/` を持つ独立したワークスペースを作成。 | `/gsd-workspace --new` |
|
||||
| `next.md` | 現在のプロジェクト状態を検出して次の論理的なステップに自動的に進む。 | `/gsd-progress --next` |
|
||||
| `node-repair.md` | タスク検証が失敗した場合の自律修復オペレーター。`execute-plan` から呼び出し。 | `execute-plan.md` (recovery) |
|
||||
|
||||
@@ -474,8 +474,8 @@ claude --dangerously-skip-permissions
|
||||
### 既存のコードベース
|
||||
|
||||
```bash
|
||||
/gsd-map-codebase # Analyse what exists (parallel agents)
|
||||
/gsd-new-project # Questions focus on what you're ADDING
|
||||
/gsd-onboard # Safely map, ingest docs, and initialize planning
|
||||
# Follow printed handoff commands, then rerun /gsd-onboard
|
||||
# (normal phase workflow from here)
|
||||
```
|
||||
|
||||
@@ -864,7 +864,8 @@ All subagent/executor commits MUST use `--no-verify`.
|
||||
themes/
|
||||
default.css # Shared CSS variables for all sketches
|
||||
MANIFEST.md # Index of all sketches with winners
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase)
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase or /gsd-onboard)
|
||||
onboarding/ # Brownfield onboarding summary (from /gsd-onboard)
|
||||
phases/
|
||||
XX-phase-name/
|
||||
XX-YY-PLAN.md # Atomic execution plans
|
||||
|
||||
@@ -44,15 +44,15 @@ claude --dangerously-skip-permissions
|
||||
|
||||
---
|
||||
|
||||
## ステップ 3 — コードベースのマッピング
|
||||
## ステップ 3 — Brownfield オンボーディングの開始
|
||||
|
||||
プロジェクトを作成する前に、GSD Core に既存のコードを学習させてください。これがブラウンフィールドの計画を正確にするステップです。
|
||||
|
||||
```text
|
||||
/gsd-map-codebase
|
||||
/gsd-onboard
|
||||
```
|
||||
|
||||
GSD Core が4つの並行マッパーサブエージェントを生成します（「Spawning 4 parallel codebase mapper agents…」という通知が表示されます。1〜5分かかりますので中断しないでください）。各エージェントはそれぞれ異なる観点に注目します:
|
||||
オンボーディングがコードベースマップ不足を示したら、推奨オプションを選び、表示された `/gsd-map-codebase` ハンドオフを実行してから `/gsd-onboard` を再実行します。`/gsd-map-codebase` が4つの並行マッパーサブエージェントを生成します（「Spawning 4 parallel codebase mapper agents…」という通知が表示されます。1〜5分かかりますので中断しないでください）。各エージェントはそれぞれ異なる観点に注目します:
|
||||
|
||||
| エージェント | 観点 |
|
||||
|-------|-------|
|
||||
@@ -133,6 +133,7 @@ Proposed Roadmap
|
||||
ROADMAP.md ← フェーズ 1、ステータス: pending
|
||||
STATE.md ← セッションメモリ
|
||||
config.json ← ワークフロー設定
|
||||
onboarding/SUMMARY.md ← onboarding status and next command
|
||||
codebase/ ← ステップ 3 の7つのマップファイル
|
||||
```
|
||||
|
||||
|
||||
@@ -51,6 +51,25 @@ v1.40에서 여섯 개의 네임스페이스 라우터가 1단계 진입점으
|
||||
|
||||
---
|
||||
|
||||
### `/gsd-onboard`
|
||||
|
||||
기존 코드베이스의 최초 GSD 온보딩을 안내합니다. 저장소 상태를 확인하고 코드베이스 매핑, 선택적 문서 수집, 프로젝트 초기화로 안전하게 넘긴 뒤 계획 파일이 준비되면 onboarding summary를 만듭니다.
|
||||
|
||||
| 플래그 | 설명 |
|
||||
|------|-------------|
|
||||
| `--fast` | 경량 `/gsd-map-codebase --fast` 매핑 handoff 우선 사용 |
|
||||
| `--text` | TUI 메뉴 대신 번호가 있는 plain-text gate 사용 |
|
||||
|
||||
**전제 조건:** 기존 저장소 또는 계획 문서. 빈 greenfield 프로젝트는 `/gsd-new-project`를 사용하세요.
|
||||
**생성 결과:** map-codebase의 `.planning/codebase/`, new-project 또는 ingest-docs의 `.planning/`, 설정 후 `.planning/onboarding/SUMMARY.md`.
|
||||
|
||||
```bash
|
||||
/gsd-onboard # 안내형 brownfield 온보딩
|
||||
/gsd-onboard --fast # 먼저 경량 코드베이스 매핑 사용
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### `/gsd-workspace`
|
||||
|
||||
GSD 워크스페이스 관리 — 리포지토리 복사본과 독립적인 `.planning/` 디렉토리를 갖는 격리된 워크스페이스 환경을 생성, 나열, 또는 삭제합니다.
|
||||
|
||||
@@ -38,6 +38,7 @@
|
||||
- [모델 프로파일](#26-model-profiles)
|
||||
- [브라운필드 기능](#brownfield-features)
|
||||
- [코드베이스 매핑](#27-codebase-mapping)
|
||||
- [기존 코드베이스 온보딩](#27b-existing-codebase-onboarding)
|
||||
- [유틸리티 기능](#utility-features)
|
||||
- [디버그 시스템](#28-debug-system)
|
||||
- [할 일 관리](#29-todo-management)
|
||||
@@ -716,7 +717,7 @@
|
||||
|
||||
**명령어:** `/gsd-map-codebase [area]`
|
||||
|
||||
**목적:** 새 프로젝트를 시작하기 전에 기존 코드베이스를 분석하여 GSD가 무엇이 존재하는지 이해하도록 합니다.
|
||||
**목적:** 새 프로젝트 시작 전 또는 `/gsd-onboard`의 매핑 handoff로 기존 코드베이스를 분석하여 GSD가 무엇이 존재하는지 이해하도록 합니다.
|
||||
|
||||
**요구사항.**
|
||||
- REQ-MAP-01: 각 분석 영역에 대한 병렬 매퍼 에이전트를 생성해야 합니다.
|
||||
@@ -736,6 +737,19 @@
|
||||
| `TESTING.md` | 테스트 인프라, 커버리지, 패턴 |
|
||||
| `INTEGRATIONS.md` | 외부 서비스, API, 서드파티 의존성 |
|
||||
|
||||
### 27b. Existing Codebase Onboarding
|
||||
|
||||
**명령어:** `/gsd-onboard [--fast] [--text]`
|
||||
|
||||
**목적:** 기존 저장소의 최초 설정을 안내하고 brownfield 상태를 확인해 코드베이스 매핑, docs 수집, 프로젝트 초기화로 안전하게 handoff합니다.
|
||||
|
||||
**요구사항.**
|
||||
- REQ-ONBOARD-01: 기존 코드, package manifest, planning 문서, 부분 `.planning/` 상태, 코드베이스 맵 누락을 감지해야 합니다.
|
||||
- REQ-ONBOARD-02: 완전한 `.planning/codebase/`가 없는 brownfield에서는 `/gsd-map-codebase` 또는 `/gsd-map-codebase --fast`로 handoff해야 합니다.
|
||||
- REQ-ONBOARD-03: ADR/PRD/SPEC/RFC 후보가 있고 project가 없으면 `/gsd-new-project` 전에 `/gsd-ingest-docs`를 제안해야 합니다.
|
||||
- REQ-ONBOARD-04: `PROJECT.md`, `REQUIREMENTS.md`, `ROADMAP.md`, `STATE.md`가 모두 있을 때까지 완료로 보고하지 않아야 합니다.
|
||||
- REQ-ONBOARD-05: project setup 후에만 `.planning/onboarding/SUMMARY.md`를 만들거나 확인해야 합니다.
|
||||
|
||||
---
|
||||
|
||||
## 유틸리티 기능
|
||||
|
||||
@@ -78,6 +78,7 @@
|
||||
| 명령어 | 역할 | 소스 |
|
||||
|---------|------|--------|
|
||||
| `/gsd-new-project` | 심층 컨텍스트 수집 및 PROJECT.md로 새 프로젝트 초기화. | [commands/gsd/new-project.md](../../commands/gsd/new-project.md) |
|
||||
| `/gsd-onboard` | 기존 코드베이스를 매핑, 문서 수집, 프로젝트 설정, onboarding summary로 안내합니다. | [commands/gsd/onboard.md](../../commands/gsd/onboard.md) |
|
||||
| `/gsd-workspace` | GSD 워크스페이스 관리 — 격리된 워크스페이스 환경을 생성(`--new`), 목록(`--list`), 또는 제거(`--remove`). | [commands/gsd/workspace.md](../../commands/gsd/workspace.md) |
|
||||
| `/gsd-discuss-phase` | 계획 전 적응형 질문을 통한 단계 컨텍스트 수집. | [commands/gsd/discuss-phase.md](../../commands/gsd/discuss-phase.md) |
|
||||
| `/gsd-mvp-phase` | 수직 MVP 슬라이스로 단계 계획 — 사용자 스토리, SPIDR 분할, 이후 plan-phase. | [commands/gsd/mvp-phase.md](../../commands/gsd/mvp-phase.md) |
|
||||
@@ -218,6 +219,7 @@
|
||||
| `milestone-summary.md` | 마일스톤 아티팩트에서 온보딩 및 검토용 마일스톤 요약 합성. | `/gsd-milestone-summary` |
|
||||
| `new-milestone.md` | 새 마일스톤 사이클 시작 — 프로젝트 컨텍스트 로드, 목표 수집, PROJECT.md/STATE.md 업데이트. | `/gsd-new-milestone` |
|
||||
| `new-project.md` | 통합 새 프로젝트 플로우 — 질문, 조사(선택), 요구사항, 로드맵. | `/gsd-new-project` |
|
||||
| `onboard.md` | Brownfield 온보딩 오케스트레이션 — 코드베이스 매핑, 문서 수집, planning 초기화, 다음 단계 요약. | `/gsd-onboard` |
|
||||
| `new-workspace.md` | 저장소 워크트리/클론과 독립적인 `.planning/`이 포함된 격리된 워크스페이스 생성. | `/gsd-workspace --new` |
|
||||
| `next.md` | 현재 프로젝트 상태를 감지하고 다음 논리적 단계로 자동 진행. | `/gsd-progress --next` |
|
||||
| `node-repair.md` | 실패한 태스크 검증을 위한 자율 수리 오퍼레이터; `execute-plan`에 의해 호출. | `execute-plan.md` (복구) |
|
||||
|
||||
@@ -474,8 +474,8 @@ claude --dangerously-skip-permissions
|
||||
### 기존 코드베이스
|
||||
|
||||
```bash
|
||||
/gsd-map-codebase # Analyse what exists (parallel agents)
|
||||
/gsd-new-project # Questions focus on what you're ADDING
|
||||
/gsd-onboard # Safely map, ingest docs, and initialize planning
|
||||
# Follow printed handoff commands, then rerun /gsd-onboard
|
||||
# (normal phase workflow from here)
|
||||
```
|
||||
|
||||
@@ -864,7 +864,8 @@ All subagent/executor commits MUST use `--no-verify`.
|
||||
themes/
|
||||
default.css # Shared CSS variables for all sketches
|
||||
MANIFEST.md # Index of all sketches with winners
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase)
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase or /gsd-onboard)
|
||||
onboarding/ # Brownfield onboarding summary (from /gsd-onboard)
|
||||
phases/
|
||||
XX-phase-name/
|
||||
XX-YY-PLAN.md # Atomic execution plans
|
||||
|
||||
@@ -49,10 +49,10 @@ claude --dangerously-skip-permissions
|
||||
프로젝트를 생성하기 전에 GSD Core가 이미 존재하는 것을 학습하도록 합니다. 이 단계가 브라운필드 계획의 정확도를 높이는 핵심입니다.
|
||||
|
||||
```text
|
||||
/gsd-map-codebase
|
||||
/gsd-onboard
|
||||
```
|
||||
|
||||
GSD Core가 4개의 병렬 매퍼 서브 에이전트를 생성합니다("Spawning 4 parallel codebase mapper agents…" 메시지가 표시되며, 1–5분 소요됩니다. 중단하지 마세요). 각 에이전트는 서로 다른 관심사에 집중합니다:
|
||||
온보딩이 코드베이스 맵 누락을 보고하면 권장 옵션을 선택하고 출력된 `/gsd-map-codebase` handoff를 실행한 뒤 `/gsd-onboard`를 다시 실행합니다. `/gsd-map-codebase`가 4개의 병렬 매퍼 서브 에이전트를 생성합니다("Spawning 4 parallel codebase mapper agents…" 메시지가 표시되며, 1–5분 소요됩니다. 중단하지 마세요). 각 에이전트는 서로 다른 관심사에 집중합니다:
|
||||
|
||||
| 에이전트 | 집중 영역 |
|
||||
|---------|---------|
|
||||
@@ -133,6 +133,7 @@ Proposed Roadmap
|
||||
ROADMAP.md ← Phase 1, 상태: pending
|
||||
STATE.md ← 세션 메모리
|
||||
config.json ← 워크플로 설정
|
||||
onboarding/SUMMARY.md ← onboarding status and next command
|
||||
codebase/ ← Step 3에서 생성된 7개의 맵 파일
|
||||
```
|
||||
|
||||
|
||||
@@ -51,6 +51,25 @@ Inicializa um novo projeto com coleta aprofundada de contexto.
|
||||
|
||||
---
|
||||
|
||||
### `/gsd-onboard`
|
||||
|
||||
Guia o onboarding inicial de um código existente no GSD. O comando verifica o estado do repositório, encaminha com segurança por mapeamento da base de código, ingestão opcional de documentos, inicialização do projeto e cria um onboarding summary quando o planejamento existe.
|
||||
|
||||
| Flag | Descrição |
|
||||
|------|-----------|
|
||||
| `--fast` | Prefere o handoff leve `/gsd-map-codebase --fast` para mapeamento |
|
||||
| `--text` | Usa gates numerados em texto puro em vez de menus TUI |
|
||||
|
||||
**Pré-requisitos:** Repositório existente ou documentos de planejamento. Para projetos greenfield vazios, use `/gsd-new-project`.
|
||||
**Produz:** `.planning/codebase/` via map-codebase, `.planning/` via new-project ou ingest-docs, e `.planning/onboarding/SUMMARY.md` após a configuração do projeto.
|
||||
|
||||
```bash
|
||||
/gsd-onboard # Onboarding brownfield guiado
|
||||
/gsd-onboard --fast # Usa primeiro o mapeamento leve da base de código
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### `/gsd-workspace`
|
||||
|
||||
Gerencia workspaces do GSD — cria, lista ou remove ambientes de workspace isolados com cópias de repositório e diretórios `.planning/` independentes.
|
||||
|
||||
@@ -68,7 +68,7 @@ Para catálogo completo e detalhamento exaustivo, consulte [FEATURES.md em ingl
|
||||
|--------|----------|
|
||||
| Projeto novo | `/gsd-new-project` -> `/gsd-discuss-phase` -> `/gsd-plan-phase` -> `/gsd-execute-phase` |
|
||||
| Correção rápida | `/gsd-quick` |
|
||||
| Código existente | `/gsd-map-codebase` -> `/gsd-new-project` |
|
||||
| Código existente | `/gsd-onboard` -> handoffs para `/gsd-map-codebase`, `/gsd-ingest-docs`, `/gsd-new-project` |
|
||||
| Fechamento de release | `/gsd-audit-milestone` -> `/gsd-complete-milestone` |
|
||||
|
||||
---
|
||||
|
||||
@@ -78,6 +78,7 @@ Esses seis roteadores são entradas apenas descritivas que o modelo seleciona pr
|
||||
| Comando | Função | Fonte |
|
||||
|---------|--------|-------|
|
||||
| `/gsd-new-project` | Inicializa um novo projeto com coleta profunda de contexto e PROJECT.md. | [commands/gsd/new-project.md](../../commands/gsd/new-project.md) |
|
||||
| `/gsd-onboard` | Guia código existente por mapeamento, ingestão de docs, configuração de projeto e onboarding summary. | [commands/gsd/onboard.md](../../commands/gsd/onboard.md) |
|
||||
| `/gsd-workspace` | Gerencia workspaces GSD — criar (`--new`), listar (`--list`) ou remover (`--remove`) ambientes de workspace isolados. | [commands/gsd/workspace.md](../../commands/gsd/workspace.md) |
|
||||
| `/gsd-discuss-phase` | Coleta contexto da fase por meio de perguntas adaptativas antes do planejamento. | [commands/gsd/discuss-phase.md](../../commands/gsd/discuss-phase.md) |
|
||||
| `/gsd-mvp-phase` | Planeja uma fase como uma fatia vertical de MVP — história de usuário, divisão SPIDR, depois plan-phase. | [commands/gsd/mvp-phase.md](../../commands/gsd/mvp-phase.md) |
|
||||
@@ -218,6 +219,7 @@ Registro completo em `get-shit-done/workflows/*.md`. Workflows são orquestrador
|
||||
| `milestone-summary.md` | Síntese do resumo do milestone — artefato de onboarding e revisão a partir dos artefatos do milestone. | `/gsd-milestone-summary` |
|
||||
| `new-milestone.md` | Inicia um novo ciclo de milestone — carregar contexto do projeto, coletar objetivos, atualizar PROJECT.md/STATE.md. | `/gsd-new-milestone` |
|
||||
| `new-project.md` | Fluxo unificado de novo projeto — questionamento, pesquisa (opcional), requisitos, roadmap. | `/gsd-new-project` |
|
||||
| `onboard.md` | Orquestração de onboarding brownfield — mapear código, ingerir docs, inicializar planning e resumir próximo passo. | `/gsd-onboard` |
|
||||
| `new-workspace.md` | Cria um workspace isolado com worktrees/clones do repositório e um `.planning/` independente. | `/gsd-workspace --new` |
|
||||
| `next.md` | Detecta o estado atual do projeto e avança automaticamente para o próximo passo lógico. | `/gsd-progress --next` |
|
||||
| `node-repair.md` | Operador de reparo autônomo para verificação de tarefa com falha; invocado por `execute-plan`. | `execute-plan.md` (recuperação) |
|
||||
|
||||
@@ -474,8 +474,8 @@ claude --dangerously-skip-permissions
|
||||
### Base de código existente
|
||||
|
||||
```bash
|
||||
/gsd-map-codebase # Analyse what exists (parallel agents)
|
||||
/gsd-new-project # Questions focus on what you're ADDING
|
||||
/gsd-onboard # Safely map, ingest docs, and initialize planning
|
||||
# Follow printed handoff commands, then rerun /gsd-onboard
|
||||
# (normal phase workflow from here)
|
||||
```
|
||||
|
||||
@@ -864,7 +864,8 @@ Para desativar a execução paralela completamente: `/gsd-settings` → defina `
|
||||
themes/
|
||||
default.css # Shared CSS variables for all sketches
|
||||
MANIFEST.md # Index of all sketches with winners
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase)
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase or /gsd-onboard)
|
||||
onboarding/ # Brownfield onboarding summary (from /gsd-onboard)
|
||||
phases/
|
||||
XX-phase-name/
|
||||
XX-YY-PLAN.md # Atomic execution plans
|
||||
|
||||
@@ -49,10 +49,10 @@ claude --dangerously-skip-permissions
|
||||
Antes de criar um projeto, deixe o GSD Core aprender o que já existe. Este é o passo que torna o planejamento brownfield preciso.
|
||||
|
||||
```text
|
||||
/gsd-map-codebase
|
||||
/gsd-onboard
|
||||
```
|
||||
|
||||
O GSD Core cria quatro sub-agentes mapeadores paralelos (você verá "Spawning 4 parallel codebase mapper agents…" — isso leva de 1 a 5 minutos; não interrompa). Cada agente foca em uma preocupação diferente:
|
||||
Se o onboarding informar que o mapa da base de código está ausente, escolha a opção recomendada e execute o handoff `/gsd-map-codebase` impresso antes de rodar `/gsd-onboard` novamente. O `/gsd-map-codebase` cria quatro sub-agentes mapeadores paralelos (você verá "Spawning 4 parallel codebase mapper agents…" — isso leva de 1 a 5 minutos; não interrompa). Cada agente foca em uma preocupação diferente:
|
||||
|
||||
| Agente | Foco |
|
||||
|--------|------|
|
||||
@@ -133,6 +133,7 @@ Aprove o roteiro.
|
||||
ROADMAP.md ← Fase 1, status: pending
|
||||
STATE.md ← memória de sessão
|
||||
config.json ← configurações do fluxo de trabalho
|
||||
onboarding/SUMMARY.md ← onboarding status and next command
|
||||
codebase/ ← os sete arquivos de mapa do Passo 3
|
||||
```
|
||||
|
||||
|
||||
@@ -23,6 +23,8 @@ The `.planning/` directory is GSD Core's shared memory for a project. Every work
|
||||
│ ├── architecture.md
|
||||
│ ├── stack.md
|
||||
│ └── ...
|
||||
├── onboarding/ # Brownfield onboarding summary (optional)
|
||||
│ └── SUMMARY.md
|
||||
├── intel/ # Queryable symbol index (optional, intel.enabled)
|
||||
│ └── API-SURFACE.md
|
||||
└── phases/
|
||||
@@ -48,7 +50,7 @@ The `.planning/` directory is GSD Core's shared memory for a project. Every work
|
||||
| | |
|
||||
|---|---|
|
||||
| **Purpose** | Canonical project identity: what it is, who it is for, core value, requirements, constraints, and key decisions. Updated throughout the project lifecycle as the product evolves. |
|
||||
| **Produced by** | `/gsd-new-project` (initial creation); updated by `/gsd-complete-milestone` as decisions are validated. |
|
||||
| **Produced by** | `/gsd-new-project` (initial creation, including `/gsd-onboard` handoff); updated by `/gsd-complete-milestone` as decisions are validated. |
|
||||
| **Consumed by** | All planning workflows; `gsd-phase-researcher`, `gsd-planner` (context); `discuss-phase` (prior decisions); `gsd-plan-checker` (project constraints). |
|
||||
|
||||
Includes an optional `## Business Context` section (Customer, Revenue model, Success metric, Strategy notes) for monetized or customer-facing projects — four one-line fields that connect business outcomes to requirement prioritization. It is deleted for internal tools, experiments, or meta workspaces, and reviewed at each milestone by `/gsd-complete-milestone` when present.
|
||||
@@ -58,7 +60,7 @@ Includes an optional `## Business Context` section (Customer, Revenue model, Suc
|
||||
| | |
|
||||
|---|---|
|
||||
| **Purpose** | Milestone and phase listing with goals, requirement IDs, success criteria, and canonical references per phase. The single source of truth for what the project is building and in what order. |
|
||||
| **Produced by** | `/gsd-new-project` (initial creation); updated by `/gsd-phase --insert` and `/gsd-complete-milestone`. |
|
||||
| **Produced by** | `/gsd-new-project` (initial creation, including `/gsd-onboard` handoff); updated by `/gsd-phase --insert` and `/gsd-complete-milestone`. |
|
||||
| **Consumed by** | `/gsd-discuss-phase`, `/gsd-plan-phase`, `/gsd-execute-phase`; all orchestration commands that need phase information; `gsd-planner`, `gsd-plan-checker`, `gsd-phase-researcher`. |
|
||||
|
||||
### `REQUIREMENTS.md`
|
||||
@@ -66,7 +68,7 @@ Includes an optional `## Business Context` section (Customer, Revenue model, Suc
|
||||
| | |
|
||||
|---|---|
|
||||
| **Purpose** | Numbered, checkable acceptance criteria for the project. Each requirement carries an ID (e.g., `AUTH-01`) that maps to roadmap phases. Marks requirements complete as phases are executed. |
|
||||
| **Produced by** | `/gsd-new-project` (initial creation); requirements marked complete by `execute-phase`. |
|
||||
| **Produced by** | `/gsd-new-project` (initial creation, including `/gsd-onboard` handoff); requirements marked complete by `execute-phase`. |
|
||||
| **Consumed by** | `gsd-planner` (plans must address all phase requirement IDs); `gsd-plan-checker` Dimension 1 (requirement coverage); `discuss-phase` (prior requirements). |
|
||||
|
||||
### `STATE.md`
|
||||
@@ -74,7 +76,7 @@ Includes an optional `## Business Context` section (Customer, Revenue model, Suc
|
||||
| | |
|
||||
|---|---|
|
||||
| **Purpose** | Living position tracker — current phase and plan, progress metrics, accumulated decisions, session continuity notes. Read at the start of every workflow run. Updated after every significant action. |
|
||||
| **Produced by** | `/gsd-new-project` (initial creation); updated continuously by all phase workflows, `/gsd-pause-work`, `/gsd-resume-work`. |
|
||||
| **Produced by** | `/gsd-new-project` (initial creation, including `/gsd-onboard` handoff); updated continuously by all phase workflows, `/gsd-pause-work`, `/gsd-resume-work`. |
|
||||
| **Consumed by** | All orchestration workflows; `/gsd-progress`; ad-hoc task execution via `/gsd-quick`; `gsd-planner` and `gsd-phase-researcher` (project decisions). |
|
||||
|
||||
See [STATE.md schema](state-md.md) for the full field reference.
|
||||
@@ -89,6 +91,14 @@ See [STATE.md schema](state-md.md) for the full field reference.
|
||||
|
||||
See [CONFIGURATION](../CONFIGURATION.md) for the complete schema.
|
||||
|
||||
### `onboarding/SUMMARY.md` (optional)
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Purpose** | Brownfield onboarding index that records artifact status, whether codebase mapping is complete, and the next recommended GSD command after first-time setup. |
|
||||
| **Produced by** | `/gsd-onboard` after `PROJECT.md`, `REQUIREMENTS.md`, `ROADMAP.md`, and `STATE.md` all exist. |
|
||||
| **Consumed by** | Humans reviewing first-time setup; future `/gsd-onboard` runs when confirming existing onboarding state. |
|
||||
|
||||
### `MILESTONES.md` (optional)
|
||||
|
||||
| | |
|
||||
|
||||
@@ -44,15 +44,21 @@ claude --dangerously-skip-permissions
|
||||
|
||||
---
|
||||
|
||||
## Step 3 — Map the codebase
|
||||
## Step 3 — Start brownfield onboarding
|
||||
|
||||
Before creating a project, let GSD Core learn what already exists. This is the step that makes brownfield planning accurate.
|
||||
Before creating a project, let GSD Core inspect the repo state and tell you the safe next top-level command. This is the step that prevents brownfield setup from skipping codebase context or overwriting existing planning files.
|
||||
|
||||
```text
|
||||
/gsd-onboard
|
||||
```
|
||||
|
||||
If code exists and `.planning/codebase/` is missing, GSD Core asks you to map the codebase first. Choose the recommended mapping option, then run the printed handoff command:
|
||||
|
||||
```text
|
||||
/gsd-map-codebase
|
||||
```
|
||||
|
||||
GSD Core spawns four parallel mapper sub-agents (you'll see "Spawning 4 parallel codebase mapper agents…" — this takes 1–5 minutes; do not interrupt). Each agent focuses on a different concern:
|
||||
Use `/gsd-onboard --fast` if you want the onboarding gate to prefer `/gsd-map-codebase --fast` for a lighter first pass. The full mapper spawns four parallel mapper sub-agents (you'll see "Spawning 4 parallel codebase mapper agents…" — this takes 1–5 minutes; do not interrupt). Each agent focuses on a different concern:
|
||||
|
||||
| Agent | Focus |
|
||||
|-------|-------|
|
||||
@@ -84,7 +90,7 @@ Open `.planning/codebase/CONCERNS.md`. This is the most useful file to read befo
|
||||
|
||||
---
|
||||
|
||||
## Step 4 — Clear context and create the project
|
||||
## Step 4 — Rerun onboarding and initialize the project
|
||||
|
||||
Clear the session window:
|
||||
|
||||
@@ -92,12 +98,20 @@ Clear the session window:
|
||||
/clear
|
||||
```
|
||||
|
||||
Now create the project. Because GSD Core found existing code in the last step, it already knows this is a brownfield project. When you run `/gsd-new-project`, the questions focus on what you are *adding*, not rebuilding what already exists:
|
||||
Now rerun onboarding:
|
||||
|
||||
```text
|
||||
/gsd-onboard
|
||||
```
|
||||
|
||||
If GSD Core detects ADRs, PRDs, specs, RFCs, or top-level requirements docs, choose the recommended docs-ingest handoff first and rerun `/gsd-onboard` afterward. Once codebase context and any existing docs are handled, onboarding prints the project-initialization handoff:
|
||||
|
||||
```text
|
||||
/gsd-new-project
|
||||
```
|
||||
|
||||
Because GSD Core found existing code in the previous step, `/gsd-new-project` knows this is a brownfield project. The questions focus on what you are *adding*, not rebuilding what already exists:
|
||||
|
||||
GSD Core asks what you want to build. Answer with the feature you are adding, not a description of the whole codebase:
|
||||
|
||||
```text
|
||||
@@ -138,6 +152,20 @@ Approve the roadmap.
|
||||
|
||||
Notice that `.planning/codebase/` is already there from Step 3. GSD Core read those files when writing `PROJECT.md`, which is why it could populate the Validated requirements without you describing them.
|
||||
|
||||
Run onboarding one more time after project setup completes:
|
||||
|
||||
```text
|
||||
/gsd-onboard
|
||||
```
|
||||
|
||||
Now that `PROJECT.md`, `REQUIREMENTS.md`, `ROADMAP.md`, and `STATE.md` all exist, onboarding creates or confirms:
|
||||
|
||||
```text
|
||||
.planning/onboarding/SUMMARY.md
|
||||
```
|
||||
|
||||
This summary is a lightweight index of the setup artifacts and the next command to run.
|
||||
|
||||
---
|
||||
|
||||
## Step 5 — Clear context and discuss Phase 1
|
||||
@@ -206,12 +234,13 @@ You now have a project with a codebase map, a discuss decision record, and verif
|
||||
/gsd-ship 1
|
||||
```
|
||||
|
||||
For every future feature, run `/gsd-map-codebase` again whenever the structure changes significantly, so the codebase map stays fresh.
|
||||
For every future feature, run `/gsd-map-codebase` again whenever the structure changes significantly, so the codebase map stays fresh. Rerun `/gsd-onboard` only when you want to re-check first-time setup completeness or regenerate the onboarding summary.
|
||||
|
||||
---
|
||||
|
||||
## What you've learned
|
||||
|
||||
- How `/gsd-onboard` safely sequences brownfield setup without nesting interactive commands or overwriting existing planning files.
|
||||
- How `/gsd-map-codebase` runs four parallel agents to produce `STACK.md`, `ARCHITECTURE.md`, `CONVENTIONS.md`, `CONCERNS.md`, `STRUCTURE.md`, `TESTING.md`, and `INTEGRATIONS.md` in `.planning/codebase/`.
|
||||
- How `/gsd-new-project` in a brownfield repo focuses questions on what you are *adding* and populates Validated requirements from existing code.
|
||||
- How the codebase map shapes every question in `/gsd-discuss-phase` — file paths, patterns, and conventions come from your actual code.
|
||||
@@ -222,5 +251,5 @@ For every future feature, run `/gsd-map-codebase` again whenever the structure c
|
||||
## Related
|
||||
|
||||
- [Your first project](your-first-project.md) — the full greenfield loop from install to PR
|
||||
- [Map codebase via Commands](../COMMANDS.md) — all `/gsd-map-codebase` flags and subcommands
|
||||
- [Commands](../COMMANDS.md) — `/gsd-onboard`, plus all `/gsd-map-codebase` flags and subcommands
|
||||
- [Documentation index](../README.md)
|
||||
|
||||
@@ -51,6 +51,25 @@ v1.40 中，六个命名空间路由器作为第一阶段入口点随附发布
|
||||
|
||||
---
|
||||
|
||||
### `/gsd-onboard`
|
||||
|
||||
引导现有代码库完成首次 GSD 接入。该命令检查仓库状态，安全地转到代码库映射、可选文档摄取、项目初始化，并在规划文件齐备后创建 onboarding summary。
|
||||
|
||||
| 标志 | 描述 |
|
||||
|------|-------------|
|
||||
| `--fast` | 优先使用轻量 `/gsd-map-codebase --fast` 映射交接 |
|
||||
| `--text` | 使用编号纯文本关卡，而不是 TUI 菜单 |
|
||||
|
||||
**前提条件：** 现有仓库或规划文档。空的绿地项目请使用 `/gsd-new-project`。
|
||||
**产出：** 由 map-codebase 生成的 `.planning/codebase/`，由 new-project 或 ingest-docs 生成的 `.planning/`，以及项目设置后的 `.planning/onboarding/SUMMARY.md`。
|
||||
|
||||
```bash
|
||||
/gsd-onboard # 引导式 brownfield 接入
|
||||
/gsd-onboard --fast # 先使用轻量代码库映射
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### `/gsd-workspace`
|
||||
|
||||
管理 GSD 工作区 — 创建、列出或移除隔离的工作区环境，包含仓库副本和独立的 `.planning/` 目录。
|
||||
|
||||
@@ -38,6 +38,7 @@
|
||||
- [模型配置](#26-model-profiles)
|
||||
- [棕地功能](#brownfield-features)
|
||||
- [代码库映射](#27-codebase-mapping)
|
||||
- [现有代码库接入](#27b-现有代码库接入)
|
||||
- [实用功能](#utility-features)
|
||||
- [调试系统](#28-debug-system)
|
||||
- [待办事项管理](#29-todo-management)
|
||||
@@ -783,7 +784,7 @@
|
||||
|
||||
**命令：** `/gsd-map-codebase [area]`
|
||||
|
||||
**目的：** 在启动新项目之前分析现有代码库，使 GSD 了解已有内容。
|
||||
**目的：** 在启动新项目之前，或作为 `/gsd-onboard` 的映射交接，分析现有代码库，使 GSD 了解已有内容。
|
||||
|
||||
**需求：**
|
||||
- REQ-MAP-01：系统必须为每个分析领域派生并行映射智能体
|
||||
@@ -805,6 +806,19 @@
|
||||
|
||||
**增量重映射 — `--paths` (#2003)：** 映射器接受可选的 `--paths <p1,p2,...>` 范围提示。提供时，它将探索限制在列出的仓库相对前缀，而非扫描整个代码树。这是执行后代码库漂移门控用于仅刷新阶段实际修改的子树的路径。每个生成的文档在其 YAML 前置元数据中携带 `last_mapped_commit`，以便相对于映射点（而非 HEAD）来测量漂移。
|
||||
|
||||
### 27b. 现有代码库接入
|
||||
|
||||
**命令：** `/gsd-onboard [--fast] [--text]`
|
||||
|
||||
**目的：** 引导现有仓库完成首次设置，检查 brownfield 状态，并安全交接到代码库映射、docs 摄取和项目初始化。
|
||||
|
||||
**需求：**
|
||||
- REQ-ONBOARD-01：系统必须检测现有代码、package manifest、规划文档、部分 `.planning/` 状态以及缺失的代码库映射文件。
|
||||
- REQ-ONBOARD-02：当 brownfield 缺少完整 `.planning/codebase/` 时，系统必须交接到 `/gsd-map-codebase` 或 `/gsd-map-codebase --fast`。
|
||||
- REQ-ONBOARD-03：当存在 ADR/PRD/SPEC/RFC 候选且 project 不存在时，系统必须在 `/gsd-new-project` 前提供 `/gsd-ingest-docs`。
|
||||
- REQ-ONBOARD-04：在 `PROJECT.md`、`REQUIREMENTS.md`、`ROADMAP.md`、`STATE.md` 全部存在前，系统不得报告 onboarding 完成。
|
||||
- REQ-ONBOARD-05：系统必须仅在 project setup 后创建或确认 `.planning/onboarding/SUMMARY.md`。
|
||||
|
||||
### 27a. 执行后代码库漂移检测
|
||||
|
||||
**引入版本：** #2003
|
||||
|
||||
@@ -78,6 +78,7 @@
|
||||
| 命令 | 角色 | 源文件 |
|
||||
|------|------|--------|
|
||||
| `/gsd-new-project` | 通过深度上下文收集和 PROJECT.md 初始化新项目。 | [commands/gsd/new-project.md](../../commands/gsd/new-project.md) |
|
||||
| `/gsd-onboard` | 引导现有代码库完成映射、文档摄取、项目设置和 onboarding summary。 | [commands/gsd/onboard.md](../../commands/gsd/onboard.md) |
|
||||
| `/gsd-workspace` | 管理 GSD 工作区 — 创建（`--new`）、列出（`--list`）或移除（`--remove`）隔离的工作区环境。 | [commands/gsd/workspace.md](../../commands/gsd/workspace.md) |
|
||||
| `/gsd-discuss-phase` | 在规划前通过自适应提问收集阶段上下文。 | [commands/gsd/discuss-phase.md](../../commands/gsd/discuss-phase.md) |
|
||||
| `/gsd-mvp-phase` | 将阶段规划为垂直 MVP 切片 — 用户故事、SPIDR 拆分，然后进行阶段规划。 | [commands/gsd/mvp-phase.md](../../commands/gsd/mvp-phase.md) |
|
||||
@@ -218,6 +219,7 @@
|
||||
| `milestone-summary.md` | 里程碑摘要综合 — 从里程碑产物生成的入职和审查产物。 | `/gsd-milestone-summary` |
|
||||
| `new-milestone.md` | 启动新里程碑周期 — 加载项目上下文、收集目标、更新 PROJECT.md/STATE.md。 | `/gsd-new-milestone` |
|
||||
| `new-project.md` | 统一的新项目流程 — 提问、研究（可选）、需求、路线图。 | `/gsd-new-project` |
|
||||
| `onboard.md` | Brownfield 接入编排 — 映射代码库、摄取文档、初始化规划并总结下一步。 | `/gsd-onboard` |
|
||||
| `new-workspace.md` | 创建带有仓库 worktree/克隆和独立 `.planning/` 的隔离工作区。 | `/gsd-workspace --new` |
|
||||
| `next.md` | 检测当前项目状态并自动推进到下一个逻辑步骤。 | `/gsd-progress --next` |
|
||||
| `node-repair.md` | 用于失败任务验证的自主修复算子；由 `execute-plan` 调用。 | `execute-plan.md`（恢复） |
|
||||
|
||||
@@ -473,8 +473,8 @@ claude --dangerously-skip-permissions
|
||||
### 现有代码库
|
||||
|
||||
```bash
|
||||
/gsd-map-codebase # Analyse what exists (parallel agents)
|
||||
/gsd-new-project # Questions focus on what you're ADDING
|
||||
/gsd-onboard # Safely map, ingest docs, and initialize planning
|
||||
# Follow printed handoff commands, then rerun /gsd-onboard
|
||||
# (normal phase workflow from here)
|
||||
```
|
||||
|
||||
@@ -863,7 +863,8 @@ All subagent/executor commits MUST use `--no-verify`.
|
||||
themes/
|
||||
default.css # Shared CSS variables for all sketches
|
||||
MANIFEST.md # Index of all sketches with winners
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase)
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase or /gsd-onboard)
|
||||
onboarding/ # Brownfield onboarding summary (from /gsd-onboard)
|
||||
phases/
|
||||
XX-phase-name/
|
||||
XX-YY-PLAN.md # Atomic execution plans
|
||||
|
||||
@@ -44,15 +44,15 @@ claude --dangerously-skip-permissions
|
||||
|
||||
---
|
||||
|
||||
## 第 3 步 — 映射代码库
|
||||
## 第 3 步 — 开始 brownfield onboarding
|
||||
|
||||
在创建项目之前，先让 GSD Core 了解已有的内容。这是使棕地规划准确的关键步骤。
|
||||
|
||||
```text
|
||||
/gsd-map-codebase
|
||||
/gsd-onboard
|
||||
```
|
||||
|
||||
GSD Core 会派生四个并行映射子代理（您将看到"Spawning 4 parallel codebase mapper agents…"——这需要 1–5 分钟；请勿中断）。每个代理专注于不同的关注点：
|
||||
如果 onboarding 报告缺少代码库映射，请选择推荐选项并运行打印出的 `/gsd-map-codebase` 交接命令，然后重新运行 `/gsd-onboard`。`/gsd-map-codebase` 会派生四个并行映射子代理（您将看到"Spawning 4 parallel codebase mapper agents…"——这需要 1–5 分钟；请勿中断）。每个代理专注于不同的关注点：
|
||||
|
||||
| 代理 | 关注点 |
|
||||
|-------|-------|
|
||||
@@ -133,6 +133,7 @@ Proposed Roadmap
|
||||
ROADMAP.md ← Phase 1, status: pending
|
||||
STATE.md ← session memory
|
||||
config.json ← workflow settings
|
||||
onboarding/SUMMARY.md ← onboarding status and next command
|
||||
codebase/ ← the seven map files from Step 3
|
||||
```
|
||||
|
||||
|
||||
@@ -166,7 +166,7 @@ and implemented by workflows/transition.md and workflows/complete-milestone.md.
|
||||
|
||||
For existing codebases:
|
||||
|
||||
1. **Map codebase first** via `/gsd:map-codebase`
|
||||
1. **Onboard or map codebase first** via `/gsd:onboard` (recommended first-time path) or `/gsd:map-codebase`
|
||||
|
||||
2. **Infer Validated requirements** from existing code:
|
||||
- What does the codebase actually do?
|
||||
|
||||
@@ -40,8 +40,9 @@ Evaluate `$ARGUMENTS` against these routing rules. Apply the **first matching**
|
||||
|
||||
| If the text describes... | Route to | Why |
|
||||
|--------------------------|----------|-----|
|
||||
| Starting a new project, "set up", "initialize" | `/gsd:new-project` | Needs full project initialization |
|
||||
| Mapping or analyzing an existing codebase | `/gsd:map-codebase` | Codebase discovery |
|
||||
| Starting a new greenfield project, "set up", "initialize" | `/gsd:new-project` | Needs full project initialization |
|
||||
| First-time setup for an existing codebase, brownfield onboarding | `/gsd:onboard` | Safe map → docs ingest → project setup sequence |
|
||||
| Mapping or analyzing an existing codebase map | `/gsd:map-codebase` | Codebase discovery or refresh |
|
||||
| A bug, error, crash, failure, or something broken | `/gsd:debug` | Needs systematic investigation |
|
||||
| Spiking, "test if", "will this work", "experiment", "prove this out", validate feasibility | `/gsd:spike` | Throwaway experiment to validate feasibility |
|
||||
| Sketching, "mockup", "what would this look like", "prototype the UI", "design this", explore visual direction | `/gsd:sketch` | Throwaway HTML mockups to explore design |
|
||||
@@ -61,7 +62,7 @@ Evaluate `$ARGUMENTS` against these routing rules. Apply the **first matching**
|
||||
| Completing a milestone, shipping, releasing | `/gsd:complete-milestone` | Milestone lifecycle |
|
||||
| A specific, actionable, small task (add feature, fix typo, update config) | `/gsd:quick` | Self-contained, single executor |
|
||||
|
||||
**Requires `.planning/` directory:** All routes except `/gsd:new-project`, `/gsd:map-codebase`, `/gsd:spike`, `/gsd:sketch`, and `/gsd:help`. If the project doesn't exist and the route requires it, suggest `/gsd:new-project` first.
|
||||
**Requires `.planning/` directory:** All routes except `/gsd:new-project`, `/gsd:onboard`, `/gsd:map-codebase`, `/gsd:spike`, `/gsd:sketch`, and `/gsd:help`. If the project doesn't exist and the route requires it, suggest `/gsd:onboard` for existing codebases or `/gsd:new-project` for greenfield projects.
|
||||
|
||||
**Ambiguity handling:** If the text could reasonably match multiple routes, ask the user via AskUserQuestion with the top 2-3 options. For example:
|
||||
|
||||
|
||||
@@ -82,7 +82,7 @@ Map an existing codebase for brownfield projects.
|
||||
- Analyzes codebase with parallel Explore agents
|
||||
- Creates `.planning/codebase/` with 7 focused documents
|
||||
- Covers stack, architecture, structure, conventions, testing, integrations, concerns
|
||||
- Use before `/gsd:new-project` on existing codebases
|
||||
- Usually reached through `/gsd:onboard` for first-time existing-codebase setup; run directly to refresh or focus a map
|
||||
|
||||
Usage: `/gsd:map-codebase`
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ Parse the first token of $ARGUMENTS:
|
||||
Check for .planning/STATE.md - loads context if project already initialized
|
||||
|
||||
**This command can run:**
|
||||
- Before /gsd-new-project (brownfield codebases) - creates codebase map first
|
||||
- Via /gsd-onboard for first-time brownfield setup - creates codebase map first
|
||||
- After /gsd-new-project (greenfield codebases) - updates codebase map as code evolves
|
||||
- Anytime to refresh codebase understanding
|
||||
</context>
|
||||
@@ -51,7 +51,7 @@ Check for .planning/STATE.md - loads context if project already initialized
|
||||
**Use map-codebase for:**
|
||||
- Brownfield projects before initialization (understand existing code first)
|
||||
- Refreshing codebase map after significant changes
|
||||
- Onboarding to an unfamiliar codebase
|
||||
- Refreshing or deepening an onboarded codebase map
|
||||
- Before major refactoring (understand current state)
|
||||
- When STATE.md references outdated codebase info
|
||||
|
||||
@@ -71,7 +71,7 @@ Check for .planning/STATE.md - loads context if project already initialized
|
||||
4. Wait for agents to complete, collect confirmations (NOT document contents)
|
||||
5. Verify all 7 documents exist with line counts
|
||||
6. Commit codebase map
|
||||
7. Offer next steps (typically: /gsd-new-project or /gsd-plan-phase)
|
||||
7. Offer next steps (typically: /gsd-onboard, /gsd-new-project, or /gsd-plan-phase)
|
||||
</process>
|
||||
|
||||
<success_criteria>
|
||||
|
||||
@@ -45,7 +45,7 @@ Display:
|
||||
|
||||
```
|
||||
Enabled (N skills, ~T tokens):
|
||||
core_loop: new-project discuss-phase plan-phase execute-phase help update
|
||||
core_loop: new-project onboard discuss-phase plan-phase execute-phase help update
|
||||
audit_review: …
|
||||
…
|
||||
|
||||
|
||||
Reference in New Issue
Block a user