@dv.nghiem/flowdeck 0.3.2 → 0.3.4

package/dist/tools/council.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"council.d.ts","sourceRoot":"","sources":["../../src/tools/council.ts"],"names":[],"mappings":"AAAA,OAAO,EAAQ,KAAK,cAAc,EAAE,MAAM,qBAAqB,CAAA;AAC/D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,kBAAkB,CAAA;AAEtD,wBAAgB,iBAAiB,CAAC,MAAM,EAAE,cAAc,GAAG,cAAc,CAmExE"}
+{"version":3,"file":"council.d.ts","sourceRoot":"","sources":["../../src/tools/council.ts"],"names":[],"mappings":"AAAA,OAAO,EAAQ,KAAK,cAAc,EAAE,MAAM,qBAAqB,CAAA;AAC/D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,kBAAkB,CAAA;AAKtD,wBAAgB,iBAAiB,CAAC,MAAM,EAAE,cAAc,GAAG,cAAc,CA2ExE"}

package/dist/tools/delegate.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"delegate.d.ts","sourceRoot":"","sources":["../../src/tools/delegate.ts"],"names":[],"mappings":"AAAA,OAAO,EAAQ,KAAK,cAAc,EAAE,MAAM,qBAAqB,CAAA;AAC/D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,kBAAkB,CAAA;AAStD,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,cAAc,GAAG,cAAc,CAiFzE"}
+{"version":3,"file":"delegate.d.ts","sourceRoot":"","sources":["../../src/tools/delegate.ts"],"names":[],"mappings":"AAAA,OAAO,EAAQ,KAAK,cAAc,EAAE,MAAM,qBAAqB,CAAA;AAC/D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,kBAAkB,CAAA;AAYtD,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,cAAc,GAAG,cAAc,CA+HzE"}

package/dist/tools/dispatch-routing.d.ts

@@ -0,0 +1,6 @@
+import type { TaskType } from "../services/model-router";
+export declare function shouldRetry(promptRes: any): boolean;
+export declare function isTransientError(text?: string): boolean;
+export declare function normalizeTaskType(taskType: string | undefined, agent: string): TaskType;
+export declare function isTaskType(value: string): value is TaskType;
+//# sourceMappingURL=dispatch-routing.d.ts.map

package/dist/tools/dispatch-routing.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"dispatch-routing.d.ts","sourceRoot":"","sources":["../../src/tools/dispatch-routing.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,0BAA0B,CAAA;AAExD,wBAAgB,WAAW,CAAC,SAAS,EAAE,GAAG,GAAG,OAAO,CAOnD;AAED,wBAAgB,gBAAgB,CAAC,IAAI,CAAC,EAAE,MAAM,GAAG,OAAO,CAUvD;AAED,wBAAgB,iBAAiB,CAAC,QAAQ,EAAE,MAAM,GAAG,SAAS,EAAE,KAAK,EAAE,MAAM,GAAG,QAAQ,CAcvF;AAED,wBAAgB,UAAU,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,QAAQ,CAY3D"}

package/dist/tools/memory-status.d.ts

@@ -0,0 +1,3 @@
+import { type ToolDefinition } from "@opencode-ai/plugin";
+export declare const memoryStatusTool: ToolDefinition;
+//# sourceMappingURL=memory-status.d.ts.map

package/dist/tools/memory-status.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"memory-status.d.ts","sourceRoot":"","sources":["../../src/tools/memory-status.ts"],"names":[],"mappings":"AAAA,OAAO,EAAQ,KAAK,cAAc,EAAE,MAAM,qBAAqB,CAAA;AAQ/D,eAAO,MAAM,gBAAgB,EAAE,cAoE7B,CAAA"}

package/dist/tools/run-pipeline.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"run-pipeline.d.ts","sourceRoot":"","sources":["../../src/tools/run-pipeline.ts"],"names":[],"mappings":"AAAA,OAAO,EAAQ,KAAK,cAAc,EAAE,MAAM,qBAAqB,CAAA;AAC/D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,kBAAkB,CAAA;AAuBtD,wBAAgB,qBAAqB,CAAC,MAAM,EAAE,cAAc,GAAG,cAAc,CAyG5E"}
+{"version":3,"file":"run-pipeline.d.ts","sourceRoot":"","sources":["../../src/tools/run-pipeline.ts"],"names":[],"mappings":"AAAA,OAAO,EAAQ,KAAK,cAAc,EAAE,MAAM,qBAAqB,CAAA;AAC/D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,kBAAkB,CAAA;AA6BtD,wBAAgB,qBAAqB,CAAC,MAAM,EAAE,cAAc,GAAG,cAAc,CAyH5E"}

package/docs/commands.md

@@ -7,18 +7,20 @@ Commands are slash commands registered in OpenCode. Run them by typing `/command
 | Command | Arguments | Description |
 |---------|-----------|-------------|
 | `/fd-new-project` | `[project-name]` | Initialize project with planning structure and default config |
+| `/fd-new-feature` | `[feature-description]` | Define a new feature and initialize feature context |
 | `/fd-discuss` | `[topic]` | Structured Q&A to capture decisions for a phase |
 | `/fd-plan` | `[--phase=N]` | Generate detailed implementation plan from decisions |
-| `/fd-new-feature` | `[feature-description]` | Full feature implementation with parallel agents |
+| `/fd-execute` | `[--phase=N] [--override]` | Implement feature with TDD pipeline and parallel agents |
+| `/fd-verify` | `[--phase=N] [--env=staging\|production]` | Verify feature completion: tests, review, security, deploy check |
 | `/fd-fix-bug` | `[bug-description]` | Debug, fix, and verify bug with regression test |
 | `/fd-deploy-check` | `[--check=deploy,review,analysis]` | Pre-deploy checks, code review, or pre-change analysis |
-| `/fd-status` | `[--roadmap | --workspace | --phase=N]` | Combined status, roadmap, and workspace view |
+| `/fd-status` | `[--roadmap \| --workspace \| --phase=N]` | Combined status, roadmap, and workspace view |
 | `/fd-resume` | `[--yes]` | Reload STATE.md and PLAN.md to continue interrupted session |
 | `/fd-checkpoint` | — | Persist current state to STATE.md |
 | `/fd-reflect` | `[--mode=reflect,learn]` | Post-session reflection or capture skill from session |
 | `/fd-map-codebase` | `[--incremental]` | Map codebase into structured `.codebase/` files |
 | `/fd-write-docs` | `[--scope=path]` | Explore APIs and generate documentation |
-| `/fd-multi-repo` | `[list | add <path> [name] | remove <name> | status]` | Multi-repo orchestration |
+| `/fd-multi-repo` | `[list \| add <path> [name] \| remove <name> \| status]` | Multi-repo orchestration |
 | `/fd-translate-intent` | `[vague intent]` | Convert vague request into ranked implementation options |
 | `/fd-ask` | `[question]` | Route question to specialist agent (architect, security, etc.) |
 | `/fd-quick` | `[task description]` | Quick focused task with automatic agent selection |
@@ -47,12 +49,38 @@ Commands are slash commands registered in OpenCode. Run them by typing `/command
 ```
 
 **What Next?**
-1. Run `/fd-discuss` to begin structured discovery
+1. Run `/fd-new-feature` to define your first feature
 2. Run `/fd-map-codebase` if this is an existing codebase
 3. Edit `.planning/config.json` directly to change settings
 
 ---
 
+## /fd-new-feature
+
+**Description:** Define a new feature and initialize feature context. This is the first step of the feature workflow after project setup.
+
+**Arguments:**
+- `[feature-description]` — name or short description of the feature
+
+**What it does:**
+1. Reads `.planning/STATE.md` to determine current phase
+2. Creates `.planning/phases/phase-N/FEATURE.md` with feature context
+3. Updates STATE.md with feature definition
+4. Displays the workflow steps ahead: discuss → plan → execute → verify
+
+**Example:**
+```
+/fd-new-feature user authentication
+```
+
+**What Next?**
+1. Run `/fd-discuss` to capture requirements
+2. Run `/fd-plan` to create implementation plan
+3. Run `/fd-execute` to implement with TDD
+4. Run `/fd-verify` to confirm all checks pass
+
+---
+
 ## /fd-discuss
 
 **Description:** Opens a structured Q&A session to capture decisions for a phase. Saves decisions to `.planning/phases/phase-N/DISCUSS.md` with D-XX numbering.
@@ -61,14 +89,14 @@ Commands are slash commands registered in OpenCode. Run them by typing `/command
 - `[topic]` — optional topic to focus the discussion
 
 **What it does:**
-1. Loads `.planning/PROJECT.md` and `.planning/STATE.md` for project context
+1. Loads `.planning/FEATURE.md` and `.planning/STATE.md` for context
 2. Invokes `@discusser` agent which asks targeted questions one at a time
 3. Records decisions with D-XX numbering (D-01, D-02, …)
 4. Saves to `.planning/phases/phase-N/DISCUSS.md`
 
 **Example:**
 ```
-/fd-discuss user authentication
+/fd-discuss
 ```
 
 **What Next?**
@@ -93,19 +121,84 @@ Commands are slash commands registered in OpenCode. Run them by typing `/command
 
 **Example:**
 ```
+/fd-plan
 /fd-plan --phase=1
 ```
 
 **What Next?**
-1. Run `/fd-new-feature` to implement
+1. Run `/fd-execute` to implement the plan
 2. Run `/fd-plan --phase=2` for next phase
 
 ---
 
-## /fd-new-feature
+## /fd-execute
+
+**Description:** Implement the current phase's plan using TDD discipline with parallel agents. This is the execution step after planning is confirmed.
+
+**Arguments:**
+- `[--phase=N]` — target specific phase
+- `[--override]` — bypass guards and proceed anyway
+
+**What it does:**
+1. Reads `.planning/phases/phase-N/PLAN.md` for implementation steps
+2. For each step, enforces TDD cycle: BEHAVIOR → RED → GREEN → REFACTOR
+3. `@tester` writes failing tests first
+4. `@coder` implements minimum to pass
+5. `@reviewer` confirms quality
+6. Updates `STATE.md` with completed steps
+7. Waves execute in order, with parallel tasks within each wave
+
+**Example:**
+```
+/fd-execute
+/fd-execute --phase=1
+```
+
+**What Next?**
+1. Run `/fd-verify` to confirm all checks pass
+2. Commit changes and create pull request
+3. Run `/fd-checkpoint` to save session state
+
+---
+
+## /fd-verify
+
+**Description:** Verify feature completion with full test suite, code review, security scan, and deploy check.
+
+**Arguments:**
+- `[--phase=N]` — target specific phase
+- `[--env=staging|production]` — environment for deploy check (default: staging)
+
+**What it does:**
+1. Runs test suite — all tests must pass
+2. Runs code review — `@reviewer` checks quality, security, conventions
+3. Runs security scan — `@security-auditor` checks for vulnerabilities
+4. Runs deploy check — build verification, CVE audit, readiness
+5. Aggregates all findings into a verification report
+6. Updates STATE.md if all checks pass
+
+**Example:**
+```
+/fd-verify
+/fd-verify --phase=1 --env=production
+```
+
+**Verdict:**
+- ✅ **VERIFIED** — all checks pass, feature is ready
+- ❌ **NOT VERIFIED** — one or more checks failed; review report and fix issues
+
+**What Next?**
+1. If VERIFIED: merge changes, deploy, or move to next phase
+2. If NOT VERIFIED: fix issues and run `/fd-verify` again
+
+---
+
+## /fd-new-feature (old — now use /fd-execute)
 
 **Description:** Implements a new feature end-to-end using TDD discipline with parallel agents. Reads active PLAN.md for context.
 
+**DEPRECATED:** Use `/fd-execute` instead. The `/fd-new-feature` command is now the entry point for defining features (step 1 of 6).
+
 **Arguments:**
 - `[feature-description]` — plain-language description of the feature
 
@@ -118,7 +211,7 @@ Commands are slash commands registered in OpenCode. Run them by typing `/command
 
 **Example:**
 ```
-/fd-new-feature "user authentication with JWT"
+/fd-execute "user authentication with JWT"
 ```
 
 ---

package/docs/installation.md

@@ -20,7 +20,7 @@ If OpenCode is not yet installed, follow the [OpenCode installation guide](https
 
 ## Method 1: curl (recommended)
 
-The install script downloads the latest release, copies all agents, skills, commands, and workflows to `~/.config/opencode/`, and registers `@dv.nghiem/flowdeck` as a plugin in `opencode.json`.
+The install script registers `@dv.nghiem/flowdeck` as a plugin in `opencode.json` and sets `orchestrator` as default agent when missing.
 
 ```bash
 curl -fsSL https://raw.githubusercontent.com/DVNghiem/flowdeck/main/install.sh | bash
@@ -29,11 +29,9 @@ curl -fsSL https://raw.githubusercontent.com/DVNghiem/flowdeck/main/install.sh |
 What the script does:
 
 1. Detects your config directory (`$OPENCODE_CONFIG_DIR` or `~/.config/opencode`)
-2. Copies `agents/*.md` → `~/.config/opencode/agent/` (markdown agents for OpenCode compatibility)
-3. Compiles TypeScript agents from `src/agents/` → `dist/agents/` (for plugin-based loading)
-4. Copies `skills/*/` → `~/.config/opencode/skills/`
-5. Registers `@dv.nghiem/flowdeck` as a plugin in `opencode.json`
-6. Sets `orchestrator` as the default agent
+2. Creates the config directory if needed
+3. Registers `@dv.nghiem/flowdeck` as a plugin in `opencode.json` if not present
+4. Sets `orchestrator` as the default agent if not already configured
 
 ---
 
@@ -59,18 +57,9 @@ Steps explained:
 
 ## Verification
 
-After any install method, run these commands to confirm everything landed correctly:
+After any install method, run these commands to confirm registration:
 
 ```bash
-# Should print 23 or more
-ls ~/.config/opencode/agent/ | grep -c "\.md"
-
-# Should list 24 or more directories
-ls ~/.config/opencode/skills/
-
-# Should list 16 or more files
-ls ~/.config/opencode/command/
-
 # Should print @dv.nghiem/flowdeck
 cat ~/.config/opencode/opencode.json | grep flowdeck
 ```
@@ -81,7 +70,7 @@ Expected output for the last command:
 "@dv.nghiem/flowdeck"
 ```
 
-If any count is lower than expected, re-run the install command. If the `opencode.json` line is missing, the plugin will not load — add it manually (see [Configuration](configuration.md)).
+If the `opencode.json` line is missing, the plugin will not load — add it manually (see [Configuration](configuration.md)).
 
 ---
 

package/docs/intelligence.md

@@ -8,19 +8,19 @@ FlowDeck's intelligence layer adds safety-first AI editing, persistent architect
 
 | Feature | Command / Hook | Storage |
 |---------|---------------|---------|
-| Change Impact Radar | `/fd-impact-radar` | VOLATILITY.json, MEMORY.json |
+| Change Impact Radar | Integrated analysis workflow | VOLATILITY.json, MEMORY.json |
 | Patch Trust Score | Hook (automatic) | VOLATILITY.json, FAILURES.json |
-| Blast Radius Preview | `/fd-blast-radius` | MEMORY.json, FAILURES.json |
+| Blast Radius Preview | Integrated analysis workflow | MEMORY.json, FAILURES.json |
 | Repo Memory Graph | `repo-memory` tool | `.codebase/MEMORY.json` |
 | Failure Replay Engine | `failure-replay` tool | `.codebase/FAILURES.json` |
 | Safe Execution Modes | Hook (automatic) | `.planning/config.json` |
-| Test Gap Detector | `/fd-test-gap` | VOLATILITY.json |
+| Test Gap Detector | Integrated analysis workflow | VOLATILITY.json |
 | Architectural Constraint Guard | Hook (automatic) | `.codebase/CONSTRAINTS.md` |
 | Intent-to-Change Translator | `/fd-translate-intent` | — |
 | Confidence-Aware Planning | Skill | — |
-| Codebase Volatility Map | `/fd-volatility-map`, `volatility-map` tool | `.codebase/VOLATILITY.json` |
-| Human Review Routing | `/fd-review-route` | VOLATILITY.json, FAILURES.json |
-| Regression Prediction | `/fd-regression-predict` | — |
+| Codebase Volatility Map | `volatility-map` tool | `.codebase/VOLATILITY.json` |
+| Human Review Routing | Integrated analysis workflow | VOLATILITY.json, FAILURES.json |
+| Regression Prediction | Integrated analysis workflow | — |
 | Decision Trace | `decision-trace` tool + hook | `.codebase/DECISIONS.jsonl` |
 | Self-Healing Policies | `policy-engine` tool | `.codebase/POLICIES.json` |
 
@@ -28,14 +28,11 @@ FlowDeck's intelligence layer adds safety-first AI editing, persistent architect
 
 ## Slash Commands
 
-### `/fd-impact-radar`
+### Change Impact Radar
 
 Predicts which files, modules, APIs, tests, and database paths are likely to be affected before the AI edits anything.
 
-```
-/fd-impact-radar --change "refactor auth token handling" --scope all
-/fd-impact-radar --change "drop users table" --json
-```
+Use `/fd-suggest` or `/fd-translate-intent` when you need pre-change analysis with impact context.
 
 **Arguments:**
 - `--change` — describe the proposed change (free text)
@@ -46,13 +43,11 @@ Predicts which files, modules, APIs, tests, and database paths are likely to be
 
 ---
 
-### `/fd-blast-radius`
+### Blast Radius Preview
 
 Shows the likely downstream consequences of a proposed change — hidden dependencies, fragile integration points, and predicted test breakages.
 
-```
-/fd-blast-radius --change "delete legacy session table" --depth 3
-```
+Use `/fd-suggest` for broad risk discovery and `/fd-deploy-check` before release changes.
 
 **Arguments:**
 - `--change` — describe the proposed change
@@ -78,14 +73,11 @@ Converts a vague request like "make checkout faster" into concrete, ranked imple
 
 ---
 
-### `/fd-volatility-map`
+### Volatility Map
 
 Displays the Codebase Volatility Map — highlights unstable zones based on churn, hotfix frequency, and unresolved TODO clusters.
 
-```
-/fd-volatility-map
-/fd-volatility-map --threshold volatile --limit 10
-```
+Use the `volatility-map` tool directly from delegated agents for incremental updates.
 
 **Arguments:**
 - `--threshold` — minimum stability level to show: `stable`, `moderate`, `volatile` (default), `critical`
@@ -96,13 +88,11 @@ Displays the Codebase Volatility Map — highlights unstable zones based on chur
 
 ---
 
-### `/fd-regression-predict`
+### Regression Prediction
 
 Estimates the most likely regression categories for a change — performance, auth, schema, UI states, async flows, etc.
 
-```
-/fd-regression-predict --change "add webhook retry logic" --categories all
-```
+FlowDeck derives regression risk from historical failures plus volatility data during analysis-oriented workflows.
 
 **Arguments:**
 - `--change` — describe the proposed change
@@ -111,14 +101,11 @@ Estimates the most likely regression categories for a change — performance, au
 
 ---
 
-### `/fd-test-gap`
+### Test Gap Detector
 
 Identifies which areas of a proposed change are weakly covered by tests, and suggests the minimum high-value tests to add first.
 
-```
-/fd-test-gap --change "add payment webhook handler"
-/fd-test-gap --change "update user schema" --scope unit
-```
+Use `/fd-verify` and `/fd-deploy-check` for current test-gap surfacing in production workflows.
 
 **Arguments:**
 - `--change` — describe the proposed change
@@ -127,13 +114,11 @@ Identifies which areas of a proposed change are weakly covered by tests, and sug
 
 ---
 
-### `/fd-review-route`
+### Human Review Routing
 
 Routes risky patches to the right reviewer type — security, backend, infra, domain-owner, frontend, data, or devops — based on the file paths and change description.
 
-```
-/fd-review-route --files "src/auth/token.ts,src/api/routes.ts" --change "new JWT rotation logic"
-```
+Routing to reviewer profiles is integrated into verification and deployment checks.
 
 **Arguments:**
 - `--files` — comma-separated file paths being changed

package/docs/optimization-baseline.md

@@ -0,0 +1,21 @@
+# FlowDeck Optimization Baseline
+
+Captured on 2026-05-07 before deep optimization implementation.
+
+## Dispatch Baseline
+
+- Command: `bun test src/tools/agent-dispatch.test.ts`
+- Result: 8 passing, 0 failing
+- Suite runtime (bun): 135ms
+- Wall clock runtime: 0.17s
+
+## Observability Baseline
+
+- `.codebase/` does not exist yet in a clean repo checkout.
+- Telemetry hooks emitted `status: "ok"` for all tool completions and did not classify failures.
+- Session/run IDs defaulted to `session-0` and `run-0` when runtime env variables were not set.
+
+## Routing and Cost Baseline
+
+- Dispatch tools did not call model routing or agent performance tracking.
+- `src/services/model-router.ts` and `src/services/agent-performance.ts` were present but not wired into `delegate`/`run-pipeline`.

package/docs/quick-start.md

@@ -71,12 +71,28 @@ All subsequent agents read these files for context. Skip this step for brand-new
 
 ---
 
-## Step 4: Start a Discussion
+## Step 4: Define a New Feature
 
-Requirements gathering comes before planning. Run:
+Before discussing requirements, initialize the feature:
 
 ```
-/fd-discuss 1
+/fd-new-feature user authentication
+```
+
+`@orchestrator` creates `.planning/phases/phase-1/FEATURE.md` and updates `STATE.md`. This establishes the feature context and shows you the next steps in the workflow:
+1. /fd-discuss
+2. /fd-plan
+3. /fd-execute
+4. /fd-verify
+
+---
+
+## Step 5: Start a Discussion
+
+Requirements gathering comes next. Run:
+
+```
+/fd-discuss
 ```
 
 `@discusser` asks structured questions about your goals, constraints, and success criteria — one question at a time. Each answer is numbered and tracked as a decision (`D-01`, `D-02`, …).
@@ -90,17 +106,17 @@ When you finish answering, the decisions are saved to `.planning/phases/phase-1/
 
 ---
 
-## Step 5: Create an Implementation Plan
+## Step 6: Create an Implementation Plan
 
 With requirements captured, generate the plan:
 
 ```
-/fd-plan 1
+/fd-plan
 ```
 
 `@planner` reads `DISCUSS.md` and produces a wave-structured `PLAN.md` in `.planning/phases/phase-1/`. Then `@plan-checker` reviews it for quality — checking that task sizes are reasonable, success criteria are specific, and wave dependencies are correct.
 
-You are shown the plan and prompted for confirmation. **Type `CONFIRMED` to allow execution to proceed.** Review carefully before confirming:
+You are shown the plan and prompted for confirmation. **Type `CONFIRM` to allow execution to proceed.** Review carefully before confirming:
 
 - Are success criteria observable and specific?
 - Are individual tasks sized to 1–3 hours?
@@ -108,40 +124,45 @@ You are shown the plan and prompted for confirmation. **Type `CONFIRMED` to allo
 
 ---
 
-## Step 6: Execute a Feature
+## Step 7: Execute the Feature
 
 Once the plan is confirmed, start implementation:
 
 ```
-/fd-new-feature "user authentication with JWT"
+/fd-execute
 ```
 
-`@orchestrator` reads `STATE.md` and `PLAN.md`, then delegates work to specialist agents in wave order:
+`@orchestrator` reads `STATE.md` and `PLAN.md`, then delegates work to specialist agents in wave order via a TDD cycle (RED → GREEN → REFACTOR):
 
-1. **Wave 1** — `@architect` designs the component structure and API contracts
-2. **Wave 2** — `@coder` and `@researcher` implement in parallel (independent tasks)
-3. **Wave 3** — `@tester` writes and runs tests against the completed implementation
-4. **Wave 4** — `@reviewer` reviews the full changeset
+1. **Behavior** — Define acceptance cases from PLAN.md
+2. **RED** — Write failing tests covering each behavior
+3. **GREEN** — Implement minimum code to pass tests
+4. **REFACTOR** — Clean up code while tests remain green
+5. **Review** — `@reviewer` checks code quality and TDD discipline
 
-You see progress updates as each wave completes. Independent tasks within a wave run simultaneously via OpenCode's multi-agent capabilities.
+You see progress updates as each task completes. Independent tasks within a wave run simultaneously.
 
 ---
 
-## Step 7: Review the Code
+## Step 8: Verify Feature Completion
 
-After implementation, run the review phase against staged changes:
+After implementation, run the full verification pipeline:
 
 ```
-/fd-review-code staged
+/fd-verify
 ```
 
-`@reviewer`, `@security-auditor`, and `@tester` run in parallel. Their findings are aggregated into a single report ranked by severity: Critical → High → Medium → Pass.
+This runs four checks in parallel:
+- **Tests** — Full test suite must pass
+- **Code Review** — `@reviewer` checks quality, security, conventions
+- **Security Scan** — `@security-auditor` checks for vulnerabilities
+- **Deploy Check** — Build verification, CVE audit, readiness assessment
 
-Address any Critical or High findings before merging.
+If all checks pass, the phase is marked **VERIFIED**. If any check fails, the report shows what needs fixing.
 
 ---
 
-## Step 8: Save State
+## Step 9: Review the Results
 
 Before closing OpenCode, checkpoint your progress:
 
@@ -161,13 +182,13 @@ This writes the current execution state to `.planning/STATE.md`. To reload conte
 
 ## Tips
 
-> **Check status at any time** — `/fd-progress` prints the current state, active plan, and a summary of recent results without modifying anything.
+> **Check status at any time** — `/fd-status` prints the current state, active plan, and a summary of recent results without modifying anything.
 
 > **Context after a restart** — always run `/fd-resume` at the start of a new OpenCode session on a project that was previously active. Agents have no memory between sessions without it.
 
-> **Follow the "What Next?" prompt** — after each FlowDeck command completes, the orchestrating agent presents a set of suggested next steps. Reading these keeps you on the intended workflow path.
+> **Follow the workflow order** — the cycle `/fd-new-feature → /fd-discuss → /fd-plan → /fd-execute → /fd-verify` ensures requirements are captured before implementation and verification happens at the end.
 
-> **Skip steps for small tasks** — for a quick bug fix, you do not need to run `/fd-discuss` and `/fd-plan`. Use `/fd-fix-bug` directly and let `@debug-specialist` handle the full cycle.
+> **Skip to execute for small tasks** — for a quick bug fix, you do not need to run `/fd-discuss` and `/fd-plan`. Use `/fd-fix-bug` directly and let `@debug-specialist` handle the full cycle.
 
 ---
 

package/docs/rules.md

@@ -1,47 +1,20 @@
 # FlowDeck Rules
 
-Rules are coding standard documents that you load into OpenCode's context. They give the AI consistent style, testing, security, and language-specific guidelines to follow across all sessions.
+Rules are coding standards used by FlowDeck agents for style, testing, security, and language-specific guidance.
 
-## How to Use Rules
+## How Rules Load
 
-### Method 1 — Project-level (recommended)
+FlowDeck loads all markdown files under `src/rules/` automatically through plugin startup. You do not need to manually copy or symlink rule files.
 
-Add the rules you want to your project's `opencode.json`. This ensures every OpenCode session in the project automatically picks them up:
+## Precedence
 
-```json
-{
-  "instructions": [
-    ".flowdeck-rules/common/coding-style.md",
-    ".flowdeck-rules/common/testing.md",
-    ".flowdeck-rules/common/security.md",
-    ".flowdeck-rules/typescript/patterns.md"
-  ]
-}
-```
-
-Where `.flowdeck-rules/` is a symlink or copy of the FlowDeck rules directory:
-
-```bash
-ln -s ~/.config/opencode/node_modules/@dv.nghiem/flowdeck/rules .flowdeck-rules
-```
-
-### Method 2 — Per-session
-
-Reference a rule file directly in your prompt:
+When guidance conflicts, precedence is:
 
-```
-Follow the rules in ~/.config/opencode/node_modules/@dv.nghiem/flowdeck/rules/typescript/patterns.md
-```
-
-### Method 3 — Copy to project
-
-Copy the rules directory into your project for version-controlled standards:
-
-```bash
-cp -r ~/.config/opencode/node_modules/@dv.nghiem/flowdeck/rules ./flowdeck-rules
-```
+1. `AGENTS.md` and `CLAUDE.md` in the repository
+2. FlowDeck plugin rules in `src/rules/**`
+3. Runtime policy rules in `.codebase/POLICIES.json`
 
-Then commit `flowdeck-rules/` to your repository so the entire team uses the same standards.
+This keeps repository-specific conventions authoritative and lets policy learning add guardrails without overriding project intent.
 
 ---