@dv.nghiem/flowdeck 0.1.1 → 0.2.0

package/dist/lib/logger.d.ts

@@ -0,0 +1,20 @@
+export interface LogEntry {
+    timestamp: string;
+    level: "info" | "warn" | "error" | "block";
+    source: string;
+    message: string;
+}
+/**
+ * Get the log file path for a given directory.
+ */
+export declare function logPath(directory: string): string;
+/**
+ * Write a log entry to .opencode/flowdeck.log
+ * Does NOT write to stdout - avoids overwriting OpenCode input box.
+ */
+export declare function logWrite(directory: string, level: LogEntry["level"], source: string, message: string): void;
+/**
+ * Read recent log entries from .opencode/flowdeck.log
+ */
+export declare function logRead(directory: string, maxEntries?: number): LogEntry[];
+//# sourceMappingURL=logger.d.ts.map

package/dist/lib/logger.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"logger.d.ts","sourceRoot":"","sources":["../../src/lib/logger.ts"],"names":[],"mappings":"AAMA,MAAM,WAAW,QAAQ;IACvB,SAAS,EAAE,MAAM,CAAA;IACjB,KAAK,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,GAAG,OAAO,CAAA;IAC1C,MAAM,EAAE,MAAM,CAAA;IACd,OAAO,EAAE,MAAM,CAAA;CAChB;AAED;;GAEG;AACH,wBAAgB,OAAO,CAAC,SAAS,EAAE,MAAM,GAAG,MAAM,CAEjD;AAWD;;;GAGG;AACH,wBAAgB,QAAQ,CACtB,SAAS,EAAE,MAAM,EACjB,KAAK,EAAE,QAAQ,CAAC,OAAO,CAAC,EACxB,MAAM,EAAE,MAAM,EACd,OAAO,EAAE,MAAM,GACd,IAAI,CAgBN;AAED;;GAEG;AACH,wBAAgB,OAAO,CAAC,SAAS,EAAE,MAAM,EAAE,UAAU,SAAK,GAAG,QAAQ,EAAE,CAuBtE"}

package/dist/tools/create-skill.d.ts

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

package/dist/tools/create-skill.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"create-skill.d.ts","sourceRoot":"","sources":["../../src/tools/create-skill.ts"],"names":[],"mappings":"AAAA,OAAO,EAAQ,KAAK,cAAc,EAAE,MAAM,qBAAqB,CAAA;AAO/D,eAAO,MAAM,eAAe,EAAE,cAgD5B,CAAA"}

package/dist/tools/reflect.d.ts

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

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

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

package/docs/agents.md

@@ -25,9 +25,8 @@ Agents are installed to `~/.config/opencode/agent/`. OpenCode loads them automat
 | [@debug-specialist](#debug-specialist) | Root cause analysis via hypothesis-driven investigation | Deep bugs that require systematic tracing |
 | [@discusser](#discusser) | Structured requirements Q&A, one question at a time | Starting new projects, defining feature scope |
 | [@doc-updater](#doc-updater) | Keeps documentation in sync with code changes | Post-implementation doc maintenance |
-| [@flowdeck-executor](#flowdeck-executor) | Step-by-step plan execution with atomic commits and state tracking | Executing confirmed PLAN.md files |
-| [@flowdeck-plan-checker](#flowdeck-plan-checker) | Validates plans before execution for completeness and feasibility | Quality gate before running a plan |
-| [@flowdeck-planner](#flowdeck-planner) | Creates detailed, wave-structured implementation plans | Creating execution-ready PLAN.md files |
+| [@plan-checker](#plan-checker) | Validates plans before execution for completeness and feasibility | Quality gate before running a plan |
+| [@planner](#planner) | Creates detailed, wave-structured implementation plans | Creating execution-ready PLAN.md files |
 | [@mapper](#mapper) | Maps codebase to `.codebase/` structured documentation | Producing STACK.md, ARCHITECTURE.md, CONVENTIONS.md, and more |
 | [@multi-repo-coordinator](#multi-repo-coordinator) | Cross-repo dependency graphs, change propagation, ordered CHANGE PLANs | Features spanning multiple microservices |
 | [@orchestrator](#orchestrator) | Coordinates multi-agent workflows, phase gating, go/no-go decisions | End-to-end feature delivery |
@@ -64,7 +63,7 @@ The architect designs systems before anyone writes code. It reads existing archi
            Read .codebase/ARCHITECTURE.md first. Save the ADR to .planning/adr/.
 ```
 
-**Works with:** `@coder` (consumes interface contracts), `@flowdeck-planner` (uses ADRs as planning input), `@multi-repo-coordinator` (defines contract-first change specs)
+**Works with:** `@coder` (consumes interface contracts), `@planner` (uses ADRs as planning input), `@multi-repo-coordinator` (defines contract-first change specs)
 
 ---
 
@@ -158,7 +157,7 @@ The debug specialist finds root causes through systematic investigation — neve
 
 ### @discusser
 
-The discusser extracts clear requirements through focused, one-at-a-time questioning. It never asks two questions in a single turn. Every decision is numbered (D-01, D-02, ...) and recorded with its rationale. If a new answer conflicts with a previous decision, it flags the conflict immediately and presents options. All decisions are saved to `.planning/phases/phase-N/DISCUSS.md` in a format that `@flowdeck-planner` can trace back to individual tasks.
+The discusser extracts clear requirements through focused, one-at-a-time questioning. It never asks two questions in a single turn. Every decision is numbered (D-01, D-02, ...) and recorded with its rationale. If a new answer conflicts with a previous decision, it flags the conflict immediately and presents options. All decisions are saved to `.planning/phases/phase-N/DISCUSS.md` in a format that `@planner` can trace back to individual tasks.
 
 **Model:** `anthropic/claude-sonnet-4-5`
 
@@ -174,7 +173,7 @@ The discusser extracts clear requirements through focused, one-at-a-time questio
            to nail down the requirements. One question at a time.
 ```
 
-**Works with:** `@flowdeck-planner` (uses DISCUSS.md as plan input), `@orchestrator` (manages the discuss phase), `@planner` (alternative for lighter planning workflows)
+**Works with:** `@planner` (uses DISCUSS.md as plan input), `@orchestrator` (manages the discuss phase), `@planner` (alternative for lighter planning workflows)
 
 ---
 
@@ -200,31 +199,9 @@ The doc updater synchronizes documentation with the current implementation after
 
 ---
 
-### @flowdeck-executor
+### @plan-checker
 
-The flowdeck executor runs confirmed PLAN.md files with discipline. It reads STATE.md, the active PLAN.md, and PROJECT.md before executing any task. Each task gets an atomic commit with a conventional commit message. If reality diverges from the plan, it documents the deviation in a `## Deviations` section rather than silently doing something different. After all tasks complete, it writes a SUMMARY.md with delivered items, verified success criteria, and deviations.
-
-**Model:** `anthropic/claude-sonnet-4-5`
-
-**Best for:**
-- Executing a confirmed phase plan step by step with checkpointed state
-- Ensuring every task in a plan is committed atomically before moving to the next
-- Documenting deviations from the plan without abandoning it
-- Generating a SUMMARY.md that makes the phase reviewable by humans
-
-**Example usage:**
-```
-@flowdeck-executor Execute phase 2. Read STATE.md for the active plan path.
-                   Checkpoint after each task and document any deviations.
-```
-
-**Works with:** `@orchestrator` (gates execution and manages phase state), `@flowdeck-plan-checker` (validates the plan before this agent runs), `@coder` (delegates implementation tasks)
-
----
-
-### @flowdeck-plan-checker
-
-The flowdeck plan checker reviews a PLAN.md before execution and returns a scored PASS or FAIL verdict. It checks three dimensions: completeness (all requirements from DISCUSS.md are covered, every task has a defined scope and success criteria), feasibility (no task exceeds 3 hours, no circular dependencies, no assumed capabilities that don't exist), and testability (each success criterion is observable, edge cases are addressed, verification commands are specified). A score of 8–10 earns PASS, 6–7 earns PASS_WITH_NOTES, and 0–5 earns FAIL.
+The plan checker reviews a PLAN.md before execution and returns a scored PASS or FAIL verdict. It checks three dimensions: completeness (all requirements from DISCUSS.md are covered, every task has a defined scope and success criteria), feasibility (no task exceeds 3 hours, no circular dependencies, no assumed capabilities that don't exist), and testability (each success criterion is observable, edge cases are addressed, verification commands are specified). A score of 8–10 earns PASS, 6–7 earns PASS_WITH_NOTES, and 0–5 earns FAIL.
 
 **Model:** `anthropic/claude-sonnet-4-5`
 
@@ -236,36 +213,11 @@ The flowdeck plan checker reviews a PLAN.md before execution and returns a score
 
 **Example usage:**
 ```
-@flowdeck-plan-checker Review .planning/phases/phase-1/PLAN.md. Score it and return
-                       PASS or FAIL with specific recommendations for any failures.
-```
-
-**Works with:** `@flowdeck-planner` (generates the plan this agent reviews), `@orchestrator` (receives the verdict and decides whether to proceed), `@flowdeck-executor` (runs the plan only after this agent passes it)
-
----
-
-### @flowdeck-planner
-
-The flowdeck planner creates execution-ready PLAN.md files with wave-structured task breakdown. Every task is scoped to specific files, sized to fit within 3 hours, and paired with a verifiable success criterion. Tasks are grouped into waves based on their dependency graph — Wave 1 contains foundation work that can run in parallel, Wave 2 gates on Wave 1, and so on. Every task traces back to a requirement from DISCUSS.md or REQUIREMENTS.md.
-
-**Model:** `anthropic/claude-sonnet-4-5`
-
-**Best for:**
-- Creating a PLAN.md for a new feature phase from DISCUSS.md decisions
-- Decomposing requirements into file-level tasks with explicit wave ordering
-- Building a dependency graph that maximizes parallel execution
-- Producing a plan that `@flowdeck-plan-checker` will score PASS on the first review
-
-**Example usage:**
-```
-@flowdeck-planner Create a PLAN.md for phase 1 using the decisions in
-                  .planning/phases/phase-1/DISCUSS.md. Group tasks into waves.
-                  Save to .planning/phases/phase-1/PLAN.md.
+@plan-checker Review .planning/phases/phase-1/PLAN.md. Score it and return
+              PASS or FAIL with specific recommendations for any failures.
 ```
 
-**Works with:** `@flowdeck-plan-checker` (reviews the plan this agent creates), `@flowdeck-executor` (runs the plan), `@orchestrator` (triggers this agent via the `/fd-plan` command)
-
----
+**Works with:** `@planner` (generates the plan this agent reviews), `@orchestrator` (receives the verdict and decides whether to proceed)
 
 ### @mapper
 
@@ -330,7 +282,7 @@ The orchestrator coordinates multi-agent execution for feature delivery. At star
               phase. Delegate incomplete steps in order and mark each complete.
 ```
 
-**Works with:** `@flowdeck-executor` (executes plan steps), `@flowdeck-plan-checker` (validates plans before execution), `@parallel-coordinator` (delegates parallel waves)
+**Works with:** `@orchestrator` (executes plan steps), `@plan-checker` (validates plans before execution), `@parallel-coordinator` (delegates parallel waves)
 
 ---
 
@@ -397,7 +349,7 @@ The planner creates detailed, file-level implementation plans with an explicit u
          Pause for my confirmation before we proceed.
 ```
 
-**Works with:** `@architect` (provides interface contracts and ADRs that feed the plan), `@coder` (executes the confirmed plan), `@flowdeck-planner` (alternative for structured FlowDeck plan format)
+**Works with:** `@architect` (provides interface contracts and ADRs that feed the plan), `@coder` (executes the confirmed plan), `@planner` (alternative for structured FlowDeck plan format)
 
 ---
 
@@ -500,7 +452,7 @@ The task splitter decomposes complex tasks into independent parallel workstreams
 - Breaking a large feature into parallel workstreams before handing off to `@parallel-coordinator`
 - Identifying which tasks must be serial (dependency gates) versus truly independent
 - Sizing and scoping tasks so each fits within a single agent session
-- Producing a wave plan when `@flowdeck-planner` is unavailable or overkill
+- Producing a wave plan when `@planner` is unavailable or overkill
 
 **Example usage:**
 ```
@@ -509,7 +461,7 @@ The task splitter decomposes complex tasks into independent parallel workstreams
                Produce a WAVE TABLE with agent assignments.
 ```
 
-**Works with:** `@parallel-coordinator` (executes the wave plan produced by this agent), `@orchestrator` (uses task breakdown to coordinate execution), `@flowdeck-planner` (complementary — planner creates PLAN.md format, splitter focuses on parallelization)
+**Works with:** `@parallel-coordinator` (executes the wave plan produced by this agent), `@orchestrator` (uses task breakdown to coordinate execution), `@planner` (complementary — planner creates PLAN.md format, splitter focuses on parallelization)
 
 ---
 

package/docs/commands.md

@@ -97,7 +97,7 @@ Commands are slash commands registered in OpenCode. Run them by typing `/command
 **What it does:**
 1. Reads `.planning/phases/phase-N/DISCUSS.md` for decisions and requirements
 2. Invokes `@planner`, which produces a detailed `PLAN.md` with tasks, dependencies, file paths, and acceptance criteria
-3. Invokes `@flowdeck-plan-checker` to validate the plan for completeness, contradiction, and missing edge cases
+3. Invokes `@plan-checker` to validate the plan for completeness, contradiction, and missing edge cases
 4. Displays the plan and any checker feedback
 5. Prompts: **type `CONFIRMED` to accept the plan and write it to disk**
 6. On confirmation, saves `.planning/phases/phase-N/PLAN.md` and updates `STATE.md`

package/docs/configuration.md

@@ -137,7 +137,7 @@ Each FlowDeck project stores its settings in `.planning/config.json`. This file
 | `workspace_mode` | `"single"` \| `"multi"` | `"single"` for one repo; `"multi"` enables the multi-repo coordinator |
 | `active_phase` | integer | The current phase number. `@orchestrator` reads this to determine which plan to execute |
 | `plan_confirmed` | boolean | Set to `true` when you type `CONFIRMED` after `/fd-plan`. Guards against unreviewed execution |
-| `enforce_guardrails` | boolean | When `true`, the `@flowdeck-plan-checker` must approve a plan before `@flowdeck-executor` runs it |
+| `enforce_guardrails` | boolean | When `true`, the `@plan-checker` must approve a plan before `@orchestrator` runs it |
 | `sub_repos` | array | List of additional repositories involved in this project (multi-repo mode only) |
 | `sub_repos[].name` | string | Short identifier used in cross-repo task delegation |
 | `sub_repos[].path` | string | Relative or absolute path to the repository on disk |
@@ -147,6 +147,85 @@ Each FlowDeck project stores its settings in `.planning/config.json`. This file
 
 ---
 
+## flowdeck.json (Agent Model Overrides)
+
+The `flowdeck.json` file lets you assign specific AI models to individual FlowDeck agents. This is useful when you want the `@planner` to use a more capable model while lighter agents like `@tester` use a faster, cheaper one.
+
+### Locations
+
+| Scope | Path |
+|-------|------|
+| Global | `~/.config/opencode/flowdeck.json` |
+| Project | `<project>/.opencode/flowdeck.json` |
+
+Project config takes precedence over global config.
+
+### Schema
+
+```json
+{
+  "agents": {
+    "<agent-name>": {
+      "model": "<provider>/<model-id>"
+    }
+  }
+}
+```
+
+### Supported Agents
+
+| Agent | Default Model | Override Example |
+|-------|--------------|-----------------|
+| `@architect` | `claude-opus-4-5` | `anthropic/claude-opus-4-5` |
+| `@build-error-resolver` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@code-explorer` | `claude-haiku-4-5` | `anthropic/claude-haiku-4-5` |
+| `@coder` | `claude-opus-4-5` | `anthropic/claude-opus-4-5` |
+| `@debug-specialist` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@discusser` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@doc-updater` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@orchestrator` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@plan-checker` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@planner` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@mapper` | `gemini-2.5-flash` | `google/gemini-2.5-flash` |
+| `@multi-repo-coordinator` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@orchestrator` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@parallel-coordinator` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@performance-optimizer` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@planner` | `claude-opus-4-5` | `anthropic/claude-opus-4-5` |
+| `@refactor-guide` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@researcher` | `gpt-4o` | `openai/gpt-4o` |
+| `@reviewer` | `gemini-2.5-flash` | `google/gemini-2.5-flash` |
+| `@security-auditor` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@task-splitter` | `claude-sonnet-4-5` | `anthropic/claude-sonnet-4-5` |
+| `@tester` | `claude-haiku-4-5` | `anthropic/claude-haiku-4-5` |
+| `@writer` | `claude-haiku-4-5` | `anthropic/claude-haiku-4-5` |
+
+### Example
+
+```json
+{
+  "agents": {
+    "planner": {
+      "model": "anthropic/claude-opus-4-5"
+    },
+    "orchestrator": {
+      "model": "anthropic/claude-sonnet-4-5"
+    },
+    "tester": {
+      "model": "anthropic/claude-haiku-4-5"
+    }
+  }
+}
+```
+
+### Notes
+
+- If an agent is not listed in `agents`, it uses the model currently selected in OpenCode.
+- Only list agents you want to override — omitted agents inherit the session default.
+- Model strings must match the format `provider/model-id` (e.g., `anthropic/claude-sonnet-4-5`).
+
+---
+
 ## Settings Command
 
 To view or modify project configuration interactively, run inside an OpenCode session:

package/docs/quick-start.md

@@ -98,7 +98,7 @@ With requirements captured, generate the plan:
 /fd-plan 1
 ```
 
-`@flowdeck-planner` reads `DISCUSS.md` and produces a wave-structured `PLAN.md` in `.planning/phases/phase-1/`. Then `@flowdeck-plan-checker` reviews it for quality — checking that task sizes are reasonable, success criteria are specific, and wave dependencies are correct.
+`@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:
 

package/docs/skills.md

@@ -35,7 +35,7 @@ For example: `@tester use the tdd-workflow skill to add tests for the payments m
 | `multi-repo` | Cross-repo dependency graphs, contract-first changes, ordered rollouts | `@multi-repo-coordinator`, `@architect` |
 | `parallel-execute` | Wave-based parallel task coordination and merge protocol | `@parallel-coordinator`, `@task-splitter` |
 | `performance-profiling` | Profiling methodology, bottleneck identification, before/after measurement | `@performance-optimizer` |
-| `plan-task` | Wave-structured task planning with dependency graph and success criteria | `@planner`, `@flowdeck-planner` |
+| `plan-task` | Wave-structured task planning with dependency graph and success criteria | `@planner`, `@planner` |
 | `python-patterns` | Python 3.10+: type hints, dataclasses, asyncio, pytest | `@coder`, `@reviewer` |
 | `refactor-guide` | Safe refactoring: tests-first, one transformation per commit | `@refactor-guide`, `@coder` |
 | `rust-patterns` | Ownership, traits, async/Tokio, error handling, smart pointers | `@coder`, `@reviewer` |

package/docs/workflows.md

@@ -37,10 +37,10 @@ Each step gates the next. `/fd-plan` will not proceed without a confirmed `DISCU
 | Workflow file | Triggered by | Agents involved |
 |--------------|-------------|----------------|
 | `discuss-flow.md` | `/fd-discuss` | `@orchestrator`, `@discusser` |
-| `plan-flow.md` | `/fd-plan` | `@orchestrator`, `@flowdeck-planner`, `@flowdeck-plan-checker` |
-| `plan-phase.md` | `/fd-plan-phase [N]` | `@flowdeck-planner`, `@flowdeck-plan-checker`, `@orchestrator` |
+| `plan-flow.md` | `/fd-plan` | `@orchestrator`, `@planner`, `@plan-checker` |
+| `plan-phase.md` | `/fd-plan-phase [N]` | `@planner`, `@plan-checker`, `@orchestrator` |
 | `execute-flow.md` | `/fd-new-feature` | `@orchestrator`, `@coder`, `@reviewer` |
-| `execute-phase.md` | `/execute-phase [N]` | `@orchestrator`, `@flowdeck-executor` |
+| `execute-phase.md` | `/execute-phase [N]` | `@orchestrator`, `@orchestrator` |
 | `fix-bug-flow.md` | `/fd-fix-bug` | `@orchestrator`, `@debug-specialist`, `@researcher`, `@tester`, `@coder`, `@reviewer` |
 | `debug-flow.md` | `/debug` | `@debug-specialist`, `@tester`, `@coder` |
 | `review-code-flow.md` | `/fd-review-code` | `@orchestrator`, `@parallel-coordinator`, `@reviewer`, `@researcher`, `@tester` |
@@ -111,15 +111,15 @@ steps:
 
 The plan flow creates an execution-ready `PLAN.md` from the decisions in a confirmed `DISCUSS.md`. It starts with a guard check — if `DISCUSS.md` does not exist or is not confirmed, execution stops and the user is directed to run `/fd-discuss` first.
 
-After loading context (`PROJECT.md`, `STATE.md`, `DISCUSS.md`), `@flowdeck-planner` creates a wave-structured `PLAN.md` where every task traces back to a `D-XX` decision. The draft plan is then handed to `@flowdeck-plan-checker`, which scores it for completeness, feasibility, and testability.
+After loading context (`PROJECT.md`, `STATE.md`, `DISCUSS.md`), `@planner` creates a wave-structured `PLAN.md` where every task traces back to a `D-XX` decision. The draft plan is then handed to `@plan-checker`, which scores it for completeness, feasibility, and testability.
 
-A FAIL verdict from `@flowdeck-plan-checker` returns the plan to `@flowdeck-planner` for revision. A PASS (or PASS_WITH_NOTES) causes `@orchestrator` to present the plan to the user. Execution **pauses here** — the plan is not saved until the user explicitly confirms it. After confirmation, the plan is saved to `.planning/phases/phase-N/PLAN.md` and `STATE.md` is updated.
+A FAIL verdict from `@plan-checker` returns the plan to `@planner` for revision. A PASS (or PASS_WITH_NOTES) causes `@orchestrator` to present the plan to the user. Execution **pauses here** — the plan is not saved until the user explicitly confirms it. After confirmation, the plan is saved to `.planning/phases/phase-N/PLAN.md` and `STATE.md` is updated.
 
 **Steps:**
 1. `@orchestrator` — Guard check: verify `DISCUSS.md` exists and is confirmed
 2. `@orchestrator` — Load `PROJECT.md`, `STATE.md`, `DISCUSS.md`
-3. `@flowdeck-planner` — Create `PLAN.md` with tasks traced to D-XX decisions
-4. `@flowdeck-plan-checker` — Verify completeness, feasibility, testability; return PASS or FAIL
+3. `@planner` — Create `PLAN.md` with tasks traced to D-XX decisions
+4. `@plan-checker` — Verify completeness, feasibility, testability; return PASS or FAIL
 5. `@orchestrator` — Present draft plan for user review
 6. `@orchestrator` — **PAUSE** — wait for explicit user CONFIRM before saving
 7. `@orchestrator` — Save confirmed `PLAN.md` to `.planning/phases/phase-N/`
@@ -133,11 +133,11 @@ A FAIL verdict from `@flowdeck-plan-checker` returns the plan to `@flowdeck-plan
 
 A focused sub-flow for creating a plan for a specific numbered phase. Unlike `plan-flow`, which drives the full `/fd-plan` command, `plan-phase` is a targeted invocation that takes a phase number as an argument and operates only on that phase's scope.
 
-`@flowdeck-planner` is spawned with the phase's `REQUIREMENTS.md` (or `DISCUSS.md`), `ROADMAP.md`, and `PROJECT.md`. It produces `.planning/phases/phase-N/PLAN.md`. `@flowdeck-plan-checker` then reviews the plan and returns PASS or FAIL with specific recommendations. Results are presented by `@orchestrator`.
+`@planner` is spawned with the phase's `REQUIREMENTS.md` (or `DISCUSS.md`), `ROADMAP.md`, and `PROJECT.md`. It produces `.planning/phases/phase-N/PLAN.md`. `@plan-checker` then reviews the plan and returns PASS or FAIL with specific recommendations. Results are presented by `@orchestrator`.
 
 **Steps:**
-1. `@flowdeck-planner` — Create `PLAN.md` for the specified phase
-2. `@flowdeck-plan-checker` — Score plan: completeness, feasibility, testability
+1. `@planner` — Create `PLAN.md` for the specified phase
+2. `@plan-checker` — Score plan: completeness, feasibility, testability
 3. `@orchestrator` — Present PASS/FAIL verdict and recommendations
 
 ---
@@ -166,14 +166,14 @@ The execute flow drives full feature delivery. A guard check verifies that `.pla
 
 A targeted sub-flow for executing a single numbered phase plan. Before delegating, `@orchestrator` verifies that `.planning/`, `.codebase/`, and `.planning/phases/phase-N/PLAN.md` all exist and that the plan has the `confirmed` status flag.
 
-`@flowdeck-executor` is spawned with `STATE.md`, `PLAN.md`, and `PROJECT.md`. It executes tasks in wave order, committing each atomically. After each task it checkpoints state via the planning-state tool. Deviations from the plan are documented in a `## Deviations` section of `PLAN.md`. After all tasks complete, `@flowdeck-executor` writes `SUMMARY.md` and `@orchestrator` marks the phase complete in `STATE.md` and `ROADMAP.md`.
+`@orchestrator` is spawned with `STATE.md`, `PLAN.md`, and `PROJECT.md`. It executes tasks in wave order, committing each atomically. After each task it checkpoints state via the planning-state tool. Deviations from the plan are documented in a `## Deviations` section of `PLAN.md`. After all tasks complete, `@orchestrator` writes `SUMMARY.md` and `@orchestrator` marks the phase complete in `STATE.md` and `ROADMAP.md`.
 
 **Steps:**
 1. `@orchestrator` — Verify prerequisites: `.planning/`, `.codebase/`, `PLAN.md` confirmed
 2. `@orchestrator` — Load `PLAN.md`, `STATE.md`, `PROJECT.md`
-3. `@flowdeck-executor` — Execute tasks in wave order; atomic commit per task
-4. `@flowdeck-executor` — Checkpoint state after each task
-5. `@flowdeck-executor` — Write `SUMMARY.md`
+3. `@orchestrator` — Execute tasks in wave order; atomic commit per task
+4. `@orchestrator` — Checkpoint state after each task
+5. `@orchestrator` — Write `SUMMARY.md`
 6. `@orchestrator` — Mark phase complete in `STATE.md` and `ROADMAP.md`
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dv.nghiem/flowdeck",
-  "version": "0.1.1",
+  "version": "0.2.0",
   "description": "FlowDeck — structured planning and execution workflows for OpenCode",
   "type": "module",
   "main": "./dist/index.js",

package/src/commands/fd-learn.md

@@ -0,0 +1,36 @@
+---
+description: Capture a repeatable pattern from this session and save it as a reusable FlowDeck skill
+argument-hint: [skill-name]
+---
+
+# Learn: Capture Session Knowledge
+
+Review what happened in this session and create a reusable skill from the most significant learning.
+
+**Input:** `$ARGUMENTS` — optional kebab-case name for the skill (the agent will choose one if omitted)
+
+## Steps
+
+1. **Identify what is worth capturing.** Look for:
+   - A novel problem that required figuring out a non-obvious solution
+   - A pattern that required human guidance or clarification to resolve
+   - A workflow or sequence that would save significant time if remembered
+   - A pitfall that was hit and corrected
+
+   If nothing significant was discovered, reply: "No new patterns to capture from this session." and stop.
+
+2. **Draft the skill.** Structure it as:
+   - `## When to Activate` — concrete triggers (e.g., "when X file pattern exists", "when the user asks about Y")
+   - `## Steps` — ordered, concrete steps to apply the skill
+   - `## Examples` — at least one short, concrete example
+   - `## Pitfalls` — common mistakes to avoid
+
+3. **Choose the skill name.** Use `$ARGUMENTS` if provided, otherwise derive a kebab-case name from the pattern.
+
+4. **Write the skill** using the `create-skill` tool with:
+   - `name`: kebab-case identifier
+   - `description`: one sentence summarising what the skill does
+   - `content`: the full Markdown body from step 2
+   - `tags`: 2–4 relevant tags
+
+5. **Report** what was captured, why it is useful, and remind the user to restart OpenCode to activate it.

package/src/commands/fd-reflect.md

@@ -0,0 +1,30 @@
+---
+description: Post-session reflection — analyse artifacts and propose self-improvement actions
+---
+
+# Reflect: Self-Improvement Analysis
+
+Analyse session artifacts and propose concrete improvements to FlowDeck's knowledge base.
+
+## Steps
+
+1. Call the `reflect` tool to gather session artifacts and generate the reflection context.
+
+2. Read the reflection context carefully:
+   - Which tools were called most often? Were any called redundantly?
+   - Which decisions were made? Do they reveal a repeatable pattern?
+   - Were there any failures? What caused them?
+   - What knowledge was absent and had to be worked out from scratch?
+
+3. **Produce improvement proposals.** For each pattern or gap found:
+
+   - **New skill** → call `create-skill` to capture it in `src/skills/`
+   - **Policy** → propose a new entry in `.codebase/POLICIES.json` for the user to review
+   - **Workflow change** → note it clearly so the user can decide
+
+4. Execute any skill creation (step 3) now.
+
+5. **Final report** — provide:
+   - What was captured (new skills created)
+   - What requires human review (policy proposals, workflow changes)
+   - 3–5 bullet summary of this session's most impactful learnings

package/src/rules/common/agent-orchestration.md

@@ -14,9 +14,7 @@ FlowDeck provides 23 specialist agents. Each has a specific role. Using the righ
 | `@debug-specialist` | Root cause analysis for bugs | When a bug needs deep investigation |
 | `@discusser` | Extract requirements via Q&A | Starting a new feature or phase |
 | `@doc-updater` | Update docs after code changes | After implementation completes |
-| `@flowdeck-executor` | Execute confirmed FlowDeck plans | When a confirmed PLAN.md exists |
-| `@flowdeck-plan-checker` | Review PLAN.md before execution | Before executing any plan |
-| `@flowdeck-planner` | Create FlowDeck PLAN.md files | When running /plan command |
+| `@plan-checker` | Review PLAN.md before execution | Before executing any plan |
 | `@mapper` | Map codebase to .codebase/ docs | Running /map-codebase |
 | `@orchestrator` | Coordinate multi-agent execution | Managing a full feature delivery |
 | `@parallel-coordinator` | Run parallel agent workstreams | When tasks can run simultaneously |
@@ -79,7 +77,7 @@ discuss → plan → execute → review
 | Phase | Agent | Command |
 |-------|-------|---------|
 | discuss | `@discusser` | `/discuss` |
-| plan | `@flowdeck-planner` → `@flowdeck-plan-checker` | `/plan` |
+| plan | `@planner` → `@plan-checker` | `/plan` |
 | execute | `@orchestrator` → `@coder`, `@tester`, etc. | `/new-feature` |
 | review | `@reviewer` + `@security-auditor` | `/review-code` |
 

package/src/workflows/execute-phase.md

@@ -1,6 +1,6 @@
 ---
 name: execute-phase
-description: "Orchestrates /execute-phase [N] — delegates to flowdeck-executor with checkpoint protocol"
+description: "Orchestrates /execute-phase [N] — delegates to orchestrator with checkpoint protocol"
 triggers:
   - /execute-phase
 steps:
@@ -10,11 +10,11 @@ steps:
   - name: load_context
     agent: "@orchestrator"
     action: Load PLAN.md, STATE.md, PROJECT.md
-  - name: delegate_to_executor
-    agent: "@flowdeck-executor"
-    action: Spawn flowdeck-executor agent to execute plan atomically
+  - name: execute_tasks
+    agent: "@orchestrator"
+    action: Delegate each task to appropriate specialist (@coder, @tester, etc.)
   - name: checkpoint_protocol
-    agent: "@flowdeck-executor"
+    agent: "@orchestrator"
     action: After each task, checkpoint state via planning-state tool
   - name: present_results
     agent: "@orchestrator"
@@ -28,7 +28,7 @@ steps:
 
 ## Purpose
 
-Execute `/execute-phase [N]` to implement a phase plan using the flowdeck-executor agent.
+Execute `/execute-phase [N]` to implement a phase plan using the orchestrator agent.
 
 ## Prerequisites
 
@@ -58,16 +58,19 @@ Read into execution context:
 - `.codebase/ARCHITECTURE.md` (if exists)
 - `.codebase/CONVENTIONS.md` (if exists)
 
-### Step 3: Delegate to flowdeck-executor
+### Step 3: Execute Tasks
 
-Spawn flowdeck-executor agent with full context.
+Orchestrator delegates each task to appropriate specialist agents:
+- @coder for implementation
+- @tester for tests
+- @researcher for research tasks
+- etc.
 
-Agent will:
-1. Execute each task in the plan
+Each task:
+1. Execute via delegated agent
 2. Run verification tests for each task
 3. Commit atomically with message: `feat(phase-N): task description`
 4. Handle deviations (document, pause for approval if checkpoint)
-5. Create SUMMARY.md after all tasks complete
 
 ### Step 4: Checkpoint Protocol
 
@@ -78,7 +81,7 @@ After each task:
 
 If session interrupted:
 - User can resume with `/resume`
-- Executor will pick up from last checkpoint
+- Orchestrator will pick up from last checkpoint
 
 ### Step 5: Present Results
 
@@ -118,7 +121,7 @@ Update ROADMAP.md:
 
 | Agent | Model | Purpose |
 |-------|-------|---------|
-| flowdeck-executor | Sonnet 4.6 | Executes plan with atomic commits |
+| orchestrator | Sonnet 4.6 | Coordinates plan execution via delegation |
 
 ## Output Files
 
@@ -139,4 +142,4 @@ If implementation requires deviating from plan:
 - If task fails: stop at checkpoint, preserve state
 - User can run `/fix-bug` or manually fix
 - Resume picks up from last successful checkpoint
-- Never leave partial state on error
+- Never leave partial state on error

package/src/workflows/plan-flow.md

@@ -12,10 +12,10 @@ steps:
     agent: "@orchestrator"
     action: Load PROJECT.md, STATE.md, DISCUSS.md with D-XX decisions
   - name: draft_plan
-    agent: "@flowdeck-planner"
+    agent: "@planner"
     action: Create PLAN.md with tasks traced to D-XX decisions from DISCUSS.md
   - name: validate_plan
-    agent: "@flowdeck-plan-checker"
+    agent: "@plan-checker"
     action: Verify all requirements covered, all D-XX decisions addressed
   - name: review_plan
     agent: "@orchestrator"