merge: sync Kilo runtime branch with main
Bring the latest main branch updates into feat/kilo-runtime-support while preserving KILO_CONFIG resolution, Kilo agent permission conversion, and relative .claude path rewrites.
This commit is contained in:
22
README.md
22
README.md
@@ -73,6 +73,8 @@ GSD fixes that. It's the context engineering layer that makes Claude Code reliab
|
||||
|
||||
People who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org.
|
||||
|
||||
Built-in quality gates catch real problems: schema drift detection flags ORM changes missing migrations, security enforcement anchors verification to threat models, and scope reduction detection prevents the planner from silently dropping your requirements.
|
||||
|
||||
---
|
||||
|
||||
## Getting Started
|
||||
@@ -94,7 +96,7 @@ Verify with:
|
||||
- Antigravity: `/gsd:help`
|
||||
|
||||
> [!NOTE]
|
||||
> Codex installation uses skills (`skills/gsd-*/SKILL.md`) rather than custom prompts.
|
||||
> Claude Code 2.1.88+ and Codex install as skills (`skills/gsd-*/SKILL.md`). Older Claude Code versions use `commands/gsd/`. The installer handles this automatically.
|
||||
|
||||
### Staying Updated
|
||||
|
||||
@@ -379,7 +381,7 @@ Or let GSD figure out the next step automatically:
|
||||
|
||||
Loop **discuss → plan → execute → verify → ship** until milestone complete.
|
||||
|
||||
If you want faster intake during discussion, use `/gsd:discuss-phase <n> --batch` to answer a small grouped set of questions at once instead of one-by-one.
|
||||
If you want faster intake during discussion, use `/gsd:discuss-phase <n> --batch` to answer a small grouped set of questions at once instead of one-by-one. Use `--chain` to auto-chain discuss into plan+execute without stopping between steps.
|
||||
|
||||
Each phase gets your input (discuss), proper research (plan), clean execution (execute), and human verification (verify). Context stays fresh. Quality stays high.
|
||||
|
||||
@@ -407,9 +409,11 @@ Quick mode gives you GSD guarantees (atomic commits, state tracking) with a fast
|
||||
|
||||
**`--research` flag:** Spawns a focused researcher before planning. Investigates implementation approaches, library options, and pitfalls. Use when you're unsure how to approach a task.
|
||||
|
||||
**`--full` flag:** Enables plan-checking (max 2 iterations) and post-execution verification.
|
||||
**`--full` flag:** Enables all phases — discussion + research + plan-checking + verification. The full GSD pipeline in quick-task form.
|
||||
|
||||
Flags are composable: `--discuss --research --full` gives discussion + research + plan-checking + verification.
|
||||
**`--validate` flag:** Enables plan-checking + post-execution verification only (the previous `--full` behavior).
|
||||
|
||||
Flags are composable: `--discuss --research --validate` gives discussion + research + plan-checking + verification.
|
||||
|
||||
```
|
||||
/gsd:quick
|
||||
@@ -512,7 +516,7 @@ You're never locked in. The system adapts.
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:new-project [--auto]` | Full initialization: questions → research → requirements → roadmap |
|
||||
| `/gsd:discuss-phase [N] [--auto] [--analyze]` | Capture implementation decisions before planning (`--analyze` adds trade-off analysis) |
|
||||
| `/gsd:discuss-phase [N] [--auto] [--analyze] [--chain]` | Capture implementation decisions before planning (`--analyze` adds trade-off analysis, `--chain` auto-chains into plan+execute) |
|
||||
| `/gsd:plan-phase [N] [--auto] [--reviews]` | Research + plan + verify for a phase (`--reviews` loads codebase review findings) |
|
||||
| `/gsd:execute-phase <N>` | Execute all plans in parallel waves, verify when complete |
|
||||
| `/gsd:verify-work [N]` | Manual user acceptance testing ¹ |
|
||||
@@ -595,8 +599,10 @@ You're never locked in. The system adapts.
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:review` | Cross-AI peer review of current phase or branch |
|
||||
| `/gsd:secure-phase [N]` | Security enforcement with threat-model-anchored verification |
|
||||
| `/gsd:pr-branch` | Create clean PR branch filtering `.planning/` commits |
|
||||
| `/gsd:audit-uat` | Audit verification debt — find phases missing UAT |
|
||||
| `/gsd:docs-update` | Verified documentation generation with doc-writer and doc-verifier agents |
|
||||
|
||||
### Backlog & Threads
|
||||
|
||||
@@ -618,7 +624,7 @@ You're never locked in. The system adapts.
|
||||
| `/gsd:debug [desc]` | Systematic debugging with persistent state |
|
||||
| `/gsd:do <text>` | Route freeform text to the right GSD command automatically |
|
||||
| `/gsd:note <text>` | Zero-friction idea capture — append, list, or promote notes to todos |
|
||||
| `/gsd:quick [--full] [--discuss] [--research]` | Execute ad-hoc task with GSD guarantees (`--full` adds plan-checking and verification, `--discuss` gathers context first, `--research` investigates approaches before planning) |
|
||||
| `/gsd:quick [--full] [--validate] [--discuss] [--research]` | Execute ad-hoc task with GSD guarantees (`--full` enables all phases, `--validate` adds plan-checking and verification, `--discuss` gathers context first, `--research` investigates approaches before planning) |
|
||||
| `/gsd:health [--repair]` | Validate `.planning/` directory integrity, auto-repair with `--repair` |
|
||||
| `/gsd:stats` | Display project statistics — phases, plans, requirements, git metrics |
|
||||
| `/gsd:profile-user [--questionnaire] [--refresh]` | Generate developer behavioral profile from session analysis for personalized responses |
|
||||
@@ -637,6 +643,7 @@ GSD stores project settings in `.planning/config.json`. Configure during `/gsd:n
|
||||
|---------|---------|---------|------------------|
|
||||
| `mode` | `yolo`, `interactive` | `interactive` | Auto-approve vs confirm at each step |
|
||||
| `granularity` | `coarse`, `standard`, `fine` | `standard` | Phase granularity — how finely scope is sliced (phases × plans) |
|
||||
| `project_code` | string | `""` | Prefix phase directories with a project code |
|
||||
|
||||
### Model Profiles
|
||||
|
||||
@@ -672,6 +679,7 @@ These spawn additional agents during planning/execution. They improve quality bu
|
||||
| `workflow.discuss_mode` | `'discuss'` | Discussion mode: `discuss` (interview), `assumptions` (codebase-first) |
|
||||
| `workflow.skip_discuss` | `false` | Skip discuss-phase in autonomous mode |
|
||||
| `workflow.text_mode` | `false` | Text-only mode for remote sessions (no TUI menus) |
|
||||
| `workflow.use_worktrees` | `true` | Toggle worktree isolation for execution |
|
||||
|
||||
Use `/gsd:settings` to toggle these, or override per-invocation:
|
||||
- `/gsd:plan-phase --skip-research`
|
||||
@@ -763,7 +771,7 @@ This prevents Claude from reading these files entirely, regardless of what comma
|
||||
|
||||
**Commands not found after install?**
|
||||
- Restart your runtime to reload commands/skills
|
||||
- Verify files exist in `~/.claude/commands/gsd/` (global) or `./.claude/commands/gsd/` (local)
|
||||
- Verify files exist in `~/.claude/skills/gsd-*/SKILL.md` (Claude Code 2.1.88+) or `~/.claude/commands/gsd/` (legacy)
|
||||
- For Codex, verify skills exist in `~/.codex/skills/gsd-*/SKILL.md` (global) or `./.codex/skills/gsd-*/SKILL.md` (local)
|
||||
|
||||
**Commands not working as expected?**
|
||||
|
||||
Reference in New Issue
Block a user