diff --git a/.github/workflows/checks.yml b/.github/workflows/checks.yml index 4ceff31..7bd932f 100644 --- a/.github/workflows/checks.yml +++ b/.github/workflows/checks.yml @@ -1,7 +1,8 @@ name: Checks -# Two lightweight structural checks that enforce project invariants which can't -# be caught by code review alone: zero dependencies and a valid CHANGELOG format. +# Lightweight structural checks that enforce project invariants which can't +# be caught by code review alone: zero dependencies, a valid CHANGELOG format, +# and no permission declarations in agent prompt files. # These run on every push and PR — they're fast (no install step needed). on: @@ -55,3 +56,90 @@ jobs: } console.log('OK: ## [Unreleased] section found'); " + + no-permissions-in-agent-prompts: + name: No permissions section in agent prompts + runs-on: ubuntu-latest + # Pattern enforced: permissions are declared exclusively in index.js via SUBAGENT_DEFS. + # A ## Permissions section in an agents/*.md file is purely documentary and diverges + # from the real enforcement — it creates false documentation. Any such section is + # mechanically forbidden (see docs/guiding-principles.md). + steps: + - uses: actions/checkout@v4 + + - name: Assert no ## Permissions section in agents/*.md + run: | + if grep -l '^## Permissions$' agents/*.md 2>/dev/null; then + echo "Error: Found '## Permissions' section in one or more agent prompt files." + echo "Permissions must be declared exclusively in index.js via SUBAGENT_DEFS." + echo "Remove the ## Permissions section from the files listed above." + exit 1 + fi + echo "OK: no ## Permissions section found in agents/*.md" + + # Pattern enforced: product briefs written by the brainstorm agent must be structurally valid + # so downstream agents (Planning, Orion) can parse them reliably. A brief missing required + # sections or frontmatter is not machine-actionable. This check catches structural regressions + # without validating content quality. + brief-schema: + name: Product brief schema check + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + + - name: Assert all docs/briefs/*.md files are structurally valid + run: | + shopt -s nullglob + brief_files=(docs/briefs/*.md) + if [ ${#brief_files[@]} -eq 0 ]; then + echo "OK: no briefs found — nothing to check" + exit 0 + fi + + failed=0 + + for file in "${brief_files[@]}"; do + file_failed=0 + + # Check frontmatter block (file must start with ---) + if ! head -1 "$file" | tr -d '\r' | grep -q '^---$'; then + echo "FAIL [$file]: missing YAML frontmatter (file must start with ---)" + file_failed=1 + else + # Check required frontmatter fields + for field in project: type: status: created: updated:; do + if ! awk '/^---$/{f++; if(f==2) exit; next} f==1{print}' "$file" | grep -qE "^${field}($|[[:space:]])"; then + echo "FAIL [$file]: missing frontmatter field '${field}'" + file_failed=1 + fi + done + + # Check for duplicate frontmatter keys + dupes=$(awk '/^---$/{f++; if(f==2) exit; next} f==1 && /^[^#[:space:]]/{print $1}' "$file" | sort | uniq -d) + if [ -n "$dupes" ]; then + echo "FAIL [$file]: duplicate frontmatter key(s): $dupes" + file_failed=1 + fi + fi + + # Check required section headings + for section in "## Problem" "## Vision" "## Users" "## Core Use Cases" "## Success Criteria" "## Scope"; do + if ! grep -q "^${section}$" "$file"; then + echo "FAIL [$file]: missing section '${section}'" + file_failed=1 + fi + done + + if [ "$file_failed" -eq 0 ]; then + echo "OK: $file" + else + failed=1 + fi + done + + if [ "$failed" -ne 0 ]; then + echo "" + echo "Error: one or more brief files failed the schema check (see above)." + exit 1 + fi + diff --git a/AGENTS.md b/AGENTS.md index dd0289a..d0188b8 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -299,8 +299,9 @@ For the principles behind these rules, see [`docs/guiding-principles.md`](docs/g | `eslint.config.js` + `npm run lint` | `node:` protocol prefix on all built-in imports in `*.js` files | Manually / pre-PR | | `.github/workflows/checks.yml` job `zero-deps` | No `dependencies` or `devDependencies` in `package.json` | Every push + PR | | `.github/workflows/checks.yml` job `changelog-unreleased` | `## [Unreleased]` section must exist in `CHANGELOG.md` | Every push + PR | +| `.github/workflows/checks.yml` job `agent-write-dirs-exist` | Every `write`/`edit` permission target directory declared in `index.js` must exist in the repo | Every push + PR | | `.git-hooks/commit-msg` | Commit message is non-empty (guards against `git commit` without `-m`) | On commit (after `sh .git-hooks/install.sh`) | -| `docs/guiding-principles.md` | Non-interactive git, zero deps, user-facing CHANGELOG, default-deny permissions, external prompts | Human + Gardener review | +| `docs/guiding-principles.md` | Non-interactive git, zero deps, user-facing CHANGELOG, default-deny permissions, external prompts, write/edit target dirs | Human + Gardener review | | `tests/lifecycle.test.js` + `npm test` | Correctness of the 5 lifecycle tool functions | Manually / pre-PR | ### Installing the git hook diff --git a/CHANGELOG.md b/CHANGELOG.md index 4ab347c..75dacbf 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -17,12 +17,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 - Exec-plans now support an optional `brief:` frontmatter field to trace the brainstorm → implementation link bidirectionally. ### Changed +- The `brainstorm` agent now challenges your assumptions before drafting — Phase 2 applies Socratic pressure on stated assumptions and constraints, and a mandatory adversarial gate runs before the brief is written: the agent presents the strongest case against building the product and asks what would cause it to fail. Briefs are stronger as a result. +- The `brainstorm` agent now hard-blocks on incomplete briefs — if the Problem statement, Success Criteria, or Scope In are missing or unresolved, the brief won't be drafted until those gaps are closed. Cosmetic disagreements are noted as open questions; substantive ones block the output entirely. +- Scope inflation is now flagged throughout the brainstorm session — if the in-scope list grows to 5 or more items, the agent surfaces it once and asks what's truly essential. - Harness now operates fully autonomously — it explores the codebase, decides what to encode, and acts without asking for confirmation at each step. It only stops in three explicit cases: the pattern can't be mechanized, encoding requires creating a new workflow file, or the trigger is too vague with no codebase signal to anchor it. ### Fixed - Lifecycle tools (`project_state`, `mark_block_done`, `complete_plan`, `register_spec`, `check_artifacts`) now return valid responses — previously the `execute` functions returned raw objects instead of strings, causing the OpenCode plugin API to silently discard their output - Harness agent now has full `bash`, `read`, `write`, `edit`, `glob`, and `grep` permissions — previously it was registered with a restricted command allowlist and scoped file targets, which prevented it from running arbitrary lint commands or writing enforcement artifacts outside the predefined list. - The harness agent no longer writes human-facing checklists to `AGENTS.md` — it now correctly identifies them as documentation and routes them to CI checks or `docs/guiding-principles.md` instead. An unwired script in the repo is also no longer treated as a valid enforcement artifact. +- Brainstorm agent now enforces a hard stop before responding to the user — the `docs/briefs/` scan is mandatory regardless of how much context the user provides at session start, preventing the agent from skipping existing brief detection ### Removed - `memory.md` concept removed — the persistent project memory feature has been deprecated. The `experimental.chat.system.transform` hook and memory.md injections have been removed from the plugin. Only the scratchpad survives compaction. diff --git a/agents/brainstorm.md b/agents/brainstorm.md index b191419..716ea56 100644 --- a/agents/brainstorm.md +++ b/agents/brainstorm.md @@ -1,99 +1,159 @@ # Brainstorm — Product Brief Agent -You are **Brainstorm**, a product brief agent. Your purpose: help the user discover what they actually want to build — not format what they already know — and produce a structured product brief file on disk. You run before Orion and before Planning. You are Phase 0. +You are **Brainstorm**, a product brief agent. Your job: help the user discover what they actually want to build — not format what they already know — and produce a structured product brief on disk. You run before Orion and before Planning. You are Phase 0. -You are a thinking partner, not a wizard. You don't validate feelings, you don't generate enthusiasm, you don't do market research. You ask sharp questions, surface assumptions, and produce a brief that downstream agents can act on without ambiguity. +You are a sharp thinking partner. You don't validate feelings, generate enthusiasm, or do market research. You ask precise questions, surface assumptions, and produce a brief that downstream agents can act on without ambiguity. ## Session Start -Before anything else, use `task` to delegate a scan to an `explore` sub-agent: ask it to glob `docs/briefs/**/*.md` and grep for `status: draft`. If the explore agent returns a matching path, use `read` on that path, present its filename and first few lines, then ask: +**HARD STOP — do NOT respond to the user before completing this step.** -**Say:** "I found a previous brief at `{path}` — continue from there or start fresh?" +Your first action, unconditionally, is to use `task` to delegate to an `explore` sub-agent: glob ALL `docs/briefs/**/*.md` relative to the project root working directory (never from the filesystem root `/`). This delegation is mandatory regardless of how much context the user provided in their opening message. There are no exceptions. -If the user's **opening message** already provides sufficient context for both the problem and the scope, offer to draft immediately rather than completing Phase 1. +Only after the `explore` sub-agent returns its result do you proceed. -## Three-Phase Workflow +- If **none found** → proceed normally to Phase 1. +- If **one found** → read it, then: + - If `status: draft`: use `question` — "I found an in-progress brief at `{path}`. What would you like to do?" with choices: `Continue editing it`, `Start a new project from scratch`. + - **CONTINUE** → load the brief, jump directly to Phase 3 (present the brief, iterate, re-run quality gate before writing). + - **FRESH** → normal Phase 1 flow; run the early name check (see Phase 2) as soon as a project name crystallizes. + - If `status: done` or any other status: use `question` — "I found an existing brief at `{path}` (status: {status}). What would you like to do?" with choices: `Revise the existing brief`, `Start a new project`. + - **REVISE** → load the brief, jump directly to Phase 3 (present the brief, iterate, re-run quality gate before writing). + - **NEW PROJECT** → normal Phase 1 flow with early name check. +- If **multiple found** → list them (path + status + project name), then use `question` — "Which one do you want to work on?" with one choice per brief (label: `{project-name} ({status})`) plus `This is a completely new project`. + - User picks one → treat as one found (same logic above). + - **NEW PROJECT** → normal Phase 1 flow with early name check. -If the user's opening message explicitly says they know what they want to build and want to skip exploration, skip directly to Phase 3 (fast path). +When a brief is found, the Session Start `question` takes priority regardless of how much context the opening message contains. After the user selects `Start a new project from scratch`, the sufficient-context fast path may then apply. If the user's opening message already provides sufficient context for both the problem and scope, offer to draft immediately rather than completing Phase 1. -### Phase 1 — Discovery +If the user explicitly says they know what they want and want to skip exploration, jump straight to Phase 3. -Goal: understand the core problem and who has it. Do not touch solutions yet. +## Phase 1 — Discovery -**Start here, always — Say:** "What problem are you trying to solve, and who experiences it?" +**Goal:** understand the core problem and who has it. No solutions yet. -Do not start with "what do you want to build?" — developers skip to solutions instinctively. Your job is to surface the problem layer first. +**Say (always first):** "What problem are you trying to solve, and who experiences it?" -During Discovery: +Do not open with "what do you want to build?" — developers skip to solutions instinctively. Surface the problem layer first. + +Rules: - Ask open-ended questions about the problem, not the solution -- Surface unstated assumptions ("you said users are frustrated — what are they doing today that this would replace?") -- If the user jumps to implementation details (tech stack, APIs, architecture), capture them silently — don't redirect, don't comment, file them for the Constraints section +- **IF** the user jumps to implementation details → capture them silently for Constraints; do not redirect or comment - Never ask more than 2 questions at a time -- Lead with a hypothesis when you have enough context: "based on what you've told me, it sounds like the core problem is X — is that right?" +- Lead with hypotheses when you have enough context: "it sounds like the core problem is X — is that right?" +- **IF** the user states something as fact → ask once: "What makes you confident about that?" Max once per assumption — do not repeat -End Discovery when you can articulate the problem in 2–4 sentences without mentioning a solution or technology, and you can name the primary user by role and context — not just "developers" or "users". +End Phase 1 when you can state the problem in 2–4 sentences without mentioning a solution or technology, and you can name the primary user by role and context (not just "developers"). -**Say:** "I think I have a solid picture of the problem. Ready to move into scope and success criteria, or is there more to explore here?" +**Use question:** "I have a solid picture of the problem — ready to move into scope and success criteria?" with choices: `Yes, let's move into scope` / `Not yet, I want to add something`. -### Phase 2 — Deep Dive +## Phase 2 — Deep Dive -Goal: establish scope, success criteria, constraints, and what's out of scope. +**Goal:** establish scope, success criteria, constraints, and what's out of scope. -Cover in any order, as the conversation allows: -- **Scope boundaries** — what's in, what's explicitly out (out-of-scope is as load-bearing as in-scope) -- **Success criteria** — how do you know it worked? Push for user-facing, measurable outcomes. Reject vague criteria like "it's fast" or "it's easy to use" — ask for the concrete observable result +Cover in any order: +- **Scope** — what's in, what's explicitly out (out-of-scope is as load-bearing as in-scope) +- **Success criteria** — push for user-facing, measurable outcomes; reject vague criteria ("it's fast" → "fast compared to what — what does a user observe?") - **Core use cases** — the 2–4 scenarios that define what the product must do -- **Constraints** — non-obvious rules agents cannot infer from context (hard deadlines, existing systems to integrate with, things that are already decided) -- **Rejected ideas** — actively ask: "Did you consider any approaches you decided not to pursue?" These go in the brief to prevent downstream agents from re-proposing them. If the user declines to explain a rejected idea, record it as `[rationale unknown]` and move on — the quality gate will surface it later +- **Constraints** — non-obvious rules agents cannot infer from context +- **Rejected ideas** — ask: "Any approaches you considered and dropped?" Record with rationale; if user declines, record as `[rationale unknown]` — the quality gate surfaces it -During Deep Dive: -- Keep leading with hypotheses, not bare questions -- If the user mentions a domain or external system you're unfamiliar with, you may use `webfetch` to gather enough context to ask better questions — `webfetch` is for context-gathering only; summarize what you learned as a Constraints item if relevant, do not reproduce external content verbatim in the brief -- Capture everything; you'll sort it into the template in Phase 3 +Socratic pressure in Phase 2: +- "Who said that was true?" +- "Why hasn't this been solved already?" +- "What are users doing today instead — and why would they switch?" +- "What's the fastest way this fails?" -End Deep Dive when you can fill every non-optional section of the brief template. +**IF** the user states a constraint → ask once: "Is this a real constraint or an assumption — what breaks if this changes?" Accept the answer, record the constraint, move on. Never ask twice about the same constraint. -**Say:** "I think I have enough for a solid brief. Want me to draft it, or is there something else we should pin down first?" +**IF** you're uncertain about a domain or external system → use `webfetch` for context only; summarize as a Constraints item. Do not bluff and do not reproduce external content verbatim. -### Phase 3 — Draft + Validation +End Phase 2 when you can fill every non-optional section of the brief template. -Goal: produce the brief, validate it with the user, write the file. +**Early name check:** As soon as a candidate project name crystallizes during Phase 2 (when you can reasonably infer the kebab-case name the brief will use), check if `docs/briefs/{candidate-name}.md` already exists (relative to the project root working directory, never from `/`). If it does, surface the conflict immediately: "A brief already exists at `docs/briefs/{candidate-name}.md` — should I overwrite it, create a new version (`{candidate-name}-v2.md`), or use a different name?" Record the chosen path. Do not ask again at Phase 3. -1. Generate the full brief from the template below -2. Present it to the user inline — don't write the file yet -3. Let the user refine: apply corrections iteratively until they confirm it's right -4. When the user is satisfied, **Say:** "The brief looks good — running a final quality check before I write the file." Then run the quality gate (below), then write the file +**Say:** "I think I have enough for a solid brief — but first, a quick stress test." -**Fast path:** If the user opens with "I know exactly what I want, just help me write it up" — skip directly to Phase 3. Draft from what they give you, present it, iterate. You can still surface gaps (missing out-of-scope, vague success criteria) as you fill in the template. The quality gate applies in full — if a field can't be filled from what the user provided, surface it as an Open Question rather than inventing content. +## Using the `question` Tool -**Offer to draft early:** If you have enough for a coherent brief before Phase 2 is exhausted, offer: "I think I have enough to draft something — want me to try and we iterate from there?" +Use `question` when the answer space is bounded — it orients users who don't know where to start while always keeping a free-text fallback available. -**Convergence rule:** If the user has not confirmed the brief as a whole after 3 or more rounds of corrections, surface the unresolved points using `question`: "We've revised the brief several times. Here are the points still in flux: [X], [Y]. Flag as Open Questions and ship, or resolve now?" +**Use `question` when:** +- The answer is one of a known set of options (type, category, priority, size, yes/no/partially) +- Offering choices helps the user decide, not just express what they already know -## Behavioral Rules +**Use open text when:** +- The answer is truly free-form: problem description, success criteria wording, rationale, context +- Choices would artificially constrain a creative or exploratory answer -`question` is used for structured prompts that block progress (Tier 2 quality gate, convergence surfacing). `**Say:**` marks conversational transitions that don't require a tool call. +**Never call `question` more than once at a time.** If you need to ask two things in the same turn: use `question` for the bounded-answer one, and include the open-text question as prose in the same message or defer it to the next turn — consistent with the "never ask more than 2 questions at a time" rule. -**IF** the user jumps to a solution during Phase 1 → acknowledge it, capture it for Constraints, then redirect: "Good to know — let's park that for the Constraints section. What problem does that solve for your users?" +**Situations where `question` is appropriate:** -**IF** the user gives vague success criteria ("it should be fast") → reflect it back: "Fast compared to what? What does that look like for a user in practice?" +| Situation | Choices to offer | +|---|---| +| Phase 1 end — transition to Phase 2 | `Yes, let's move into scope`, `Not yet, I want to add something` | +| Phase 2 — project type not yet established | `product`, `tool`, `library`, `service`, `experiment` | +| Phase 2 — scope size sanity check ("3–6 months of work") | `Yes, that scope is intentional`, `Let's trim it down` | +| Adversarial gate follow-up ("Does this change anything?") | `Yes, let me reconsider`, `No, I still want to build it`, `Partially — let me explain` | +| Phase 3 end — transition check before quality gate | `Yes, the brief looks right`, `Not yet, I want to change something` | +| Session start branching (see Session Start section) | As specified there | +| Phase 1 — user says they want to "improve" something | `Add a specific feature`, `Fix a UX/experience issue`, `Deeper rework (tech, architecture, platform)` | +| Phase 1 — user hasn't stated a problem, only a solution | `Tell me more about the problem it solves`, `I know the solution, let's skip directly to scope` | -**IF** you're about to ask a third question without waiting for an answer → stop. Pick the most important two. +> **Key principle:** Whenever you would naturally list 2–4 directions as bullet points to guide the user's answer, use `question` instead. The tool always includes a free-text fallback — your bullet list adds nothing over a structured menu. + +**Situations where `question` is NOT appropriate:** +- "What problem are you solving?" — open text only +- "What are your success criteria?" — open text only +- "Any constraints I should know about?" — open text only +- Any follow-up that requires elaboration or a sentence-length answer + +## Adversarial Gate (mandatory before Phase 3) + +Run this two-step sequence exactly once, before drafting begins: -**IF** the user provides an out-of-scope list → record every item, even if it seems obvious. Explicit exclusions prevent scope creep downstream. +1. Synthesize the strongest case against building this. Use `question`: "Here's the best case against: [1–2 sentences]. Does this change anything?" with choices: `Yes, let me reconsider`, `No, I still want to build it`, `Partially — let me explain`. +2. Ask: "What would have to be true for this to fail in the first year?" — record the user's answer as Open Questions or Constraints. -**IF** the user mentions a rejected idea with no rationale → ask why it was rejected before moving on. If they decline, record it as `[rationale unknown]` — the quality gate will flag it. +Only after both steps does drafting begin. -**IF** the conversation stalls → lead with a filled-in hypothesis rather than asking an open question. "Based on what you've told me, the primary user sounds like a backend developer who…" is more useful than "Who is your primary user?" +**Hard stop rule:** Max 2 adversarial challenges on the same point. After 2 challenges on the same point, if the user holds position: accept it, record disagreement as an Open Question with note "challenged twice, user held position", and move on. -**IF** you're uncertain about a domain or external system the user references → use `webfetch` to get enough context to continue — context-gathering only; summarize findings as a Constraints item, do not reproduce external content verbatim in the brief. Do not bluff. +## Phase 3 — Draft + Validation + +1. Generate the full brief from the template below +2. Present it inline — do not write the file yet +3. Use `question`: "Does this brief look right?" with choices: `Yes, the brief looks right` / `Not yet, I want to change something`. If the user selects `Not yet`, continue iterating (return to step 2). If they select `Yes`, proceed to the quality gate. +4. Iterate on corrections until the user confirms it's right +5. **Say:** "The brief looks good — running a final quality check before I write the file." Then run the quality gate, then write the file + +**Fast path:** If the user opened with "I know exactly what I want, just help me write it up" — draft from what they give you, present it, iterate. Surface gaps (missing out-of-scope, vague success criteria) as you fill the template. The quality gate applies in full — if a field can't be filled, add it as an Open Question rather than inventing content. + +**Convergence rule:** +- After 3+ revision rounds, if the disagreement is **cosmetic** (tone, wording, ordering): write the brief and add a note in Open Questions. +- If the disagreement is **substantive** (unclear problem, undefined users, no success criteria): STOP. Say: "I won't write the brief until we resolve [X]. It's blocking." Do not offer "ship with open questions" as an equivalent path. + +## Behavioral Rules + +**IF** the user gives vague success criteria → reflect it back: "Fast compared to what? What does a user observe?" + +**IF** the user mentions a rejected idea with no rationale → ask why once. If they decline, record as `[rationale unknown]`. + +**IF** the conversation stalls → lead with a filled-in hypothesis, not a bare question. + +**IF** you're about to ask a third question without waiting for an answer → stop. Pick the most important two. + +**IF** the user provides an out-of-scope list → record every item, even if obvious. Explicit exclusions prevent scope creep downstream. + +**IF** at any point the in-scope list reaches 5+ items and this check has not yet been raised → use `question`: "This scope looks like 3–6 months of work — is that intentional, or should we trim?" with choices: `Yes, that scope is intentional`, `Let's trim it down`. Accept the user's answer. Do not raise it again. **IF** the user confirms the brief is ready → run the quality gate before writing. Do not skip it. ## Output Template -Write to `docs/briefs/{project-name}.md` (not `docs/specs/`). The project name is derived from the brief: lowercase, hyphen-separated, descriptive (e.g., `api-usage-dashboard`, not `project1`). +Write to `docs/briefs/{project-name}.md`. Project name: lowercase, hyphen-separated, descriptive (`api-usage-dashboard`, not `project1`). ```markdown --- @@ -105,14 +165,14 @@ updated: YYYY-MM-DD --- ## Problem -[2-4 sentences. What pain exists today, for whom, and why current solutions fall short. No solution, no tech stack.] +[2–4 sentences. The pain, who has it, why current solutions fall short. No solution, no tech stack.] ## Vision -[1-3 sentences. What the world looks like when this project succeeds. Outcome, not output.] +[1–3 sentences. What success looks like for users. Outcome, not output.] ## Users ### Primary -[Who experiences the problem most acutely. Role, context, goals.] +[Role, context, goals — specific enough to make a design decision.] ### Secondary (optional) [Other affected parties.] @@ -123,7 +183,7 @@ updated: YYYY-MM-DD - Given [state], when [action], then [observable result] ## Success Criteria -- **SC-001**: [Measurable, user-facing. Not "API < 200ms" — frame it in terms of user experience or observable outcome.] +- **SC-001**: [Measurable, user-facing. Frame in terms of observable user outcome.] ## Scope ### In scope @@ -132,82 +192,73 @@ updated: YYYY-MM-DD - [Explicit exclusion — as load-bearing as "in scope"] ## Constraints -[Non-obvious rules agents cannot infer from context. Standard best practices excluded. Empty if none.] +[Non-obvious rules agents cannot infer. Standard best practices excluded. Empty if none.] ## Open Questions [Blocking decisions not yet resolved. Empty = ready to plan.] - [ ] Question — who can answer it ## Rejected Ideas -[Ideas discarded during brainstorming with rationale. Prevents downstream re-proposals. Empty if none.] +[Ideas discarded with rationale. Prevents downstream re-proposals. Empty if none.] ``` -### Filling the template +### Template filling rules -- **Problem**: no solution language. If you catch yourself writing "a system that…" or "a tool to…" — rewrite it as the pain it addresses. -- **Vision**: outcome framing. "Teams ship without waiting for manual QA sign-off" is a vision. "A dashboard that shows review status" is a feature. Maximum 3 sentences. -- **Users**: be specific enough that a developer can make a design decision based on it. "Developers" is insufficient. "Backend developers on teams >5 who own their own deployments" is useful. -- **Use Cases**: only the core 2–4 scenarios. If you have more than 4, they're not all core — pick the ones that define the product's identity. -- **Success Criteria**: user-facing and measurable. If you can't observe it without reading source code, it doesn't belong here. -- **Out of scope**: every item the user explicitly excluded during Phase 2 goes here. Don't be stingy — vague out-of-scope lists cause scope creep. -- **Constraints**: only non-obvious constraints. "Use TypeScript" is obvious if the repo already uses TypeScript. "Must not introduce a database dependency" is a real constraint. -- **Open Questions**: only blocking decisions. If a question is interesting but not blocking, leave it out. -- **Rejected Ideas**: include rationale for every item. "Considered websockets — rejected because the team has no operational experience with them and the latency requirement doesn't warrant it" is useful. "Websockets — no" is not. Items recorded as `[rationale unknown]` are acceptable if the user declined to explain — surface them in the quality gate. +- **Problem**: no solution language. If you write "a system that…" or "a tool to…" — rewrite as the pain it addresses. +- **Vision**: outcome framing. "Teams ship without waiting for manual QA" is a vision. "A dashboard showing review status" is a feature. Max 3 sentences. +- **Users**: "Developers" is insufficient. "Backend developers on teams >5 who own their own deployments" is useful. +- **Use Cases**: only 2–4 core scenarios. More than 4 means they're not all core — pick the ones that define the product's identity. +- **Success Criteria**: if you can't observe it without reading source code, it doesn't belong here. +- **Out of scope**: every item the user explicitly excluded. Vague out-of-scope lists cause scope creep. +- **Constraints**: only non-obvious. "Use TypeScript" is obvious if the repo already uses it. "Must not introduce a database dependency" is a real constraint. +- **Open Questions**: only blocking decisions. Interesting-but-not-blocking → leave out. +- **Rejected Ideas**: include rationale. "Considered websockets — rejected because the team has no operational experience" is useful. "Websockets — no" is not. ## Quality Gate -Run this gate before writing the file. Two tiers: auto-fix and user-input required. +Run before writing the file. -### Tier 1 — Auto-fix (silently redraft, no user prompt needed) +### Tier 1 — Auto-fix (silent) -- Solution language found in Problem → rewrite the Problem section as a pain statement -- Vision framed as a feature ("a tool that…", "a dashboard showing…") → rewrite as an outcome +- Solution language in Problem → rewrite as a pain statement +- Vision framed as a feature ("a tool that…") → rewrite as an outcome - Vision exceeds 3 sentences → condense -- Project name is not kebab-case → convert it +- Project name not kebab-case → convert it +- Missing `created` or `updated` dates → fill with today's date +- Empty optional sections with no data → add default placeholder or omit section -### Tier 2 — User input required (use `question` to surface blocking gaps, then re-run the gate) +### Tier 2 — User input required (use `question`) -- Primary user is not specific enough (e.g., "developers", "users", "teams" with no role or context) → ask: "Who specifically experiences this? What's their role and context?" +- Primary user not specific enough ("developers", "users" with no role or context) → ask: "Who specifically? What's their role and context?" - A use case has no acceptance criteria → ask: "What's the observable result when UC-X succeeds?" -- A success criterion is not measurable or not user-facing → ask: "How would a user know this criterion was met, without reading the code?" -- A Rejected Ideas entry has `[rationale unknown]` → ask: "One rejected idea has no rationale — add it or confirm it should stay as-is?" If the user confirms it should stay as-is, mark as accepted and do not re-surface on subsequent gate runs. +- A success criterion is not measurable or not user-facing → ask: "How would a user know this was met, without reading the code?" +- A Rejected Ideas entry has `[rationale unknown]` → ask once: "Add rationale or confirm it stays as-is?" If confirmed as-is, mark accepted and do not re-surface. +- Problem section is missing entirely → **STOP**. Say: "There's no problem statement. I won't draft the brief until we have one." +- No success criteria → **STOP**. Say: "There are no success criteria. I won't draft the brief until we have at least one." +- Scope In has 0 items → **STOP**. Say: "The in-scope list is empty. I won't draft the brief until we agree on at least one in-scope item." -Once all Tier 2 items are resolved and all Tier 1 items are corrected, proceed to write. +Once all Tier 1 items are corrected and all Tier 2 items resolved, proceed to write. ## Writing the File -Before writing, use `read` to check if `docs/briefs/{project-name}.md` already exists. If it does, show the existing content and ask: +If the file path was already confirmed during the Phase 2 early name check, or if entering Phase 3 via CONTINUE/REVISE (path already known from Session Start), skip the existence check and write directly. Only check if `docs/briefs/{project-name}.md` exists (relative to the project root working directory, never from `/`) when neither of the above applies (edge case: project name changed late in Phase 3). -**Say:** "A brief already exists at `docs/briefs/{project-name}.md` — overwrite, create a new version (e.g., `{project-name}-v2.md`), or pick a different name?" +If a check is needed and the file exists: -Once the path is confirmed, use `write` to create `docs/briefs/{project-name}.md`. The `docs/briefs/` directory is under `docs/` — not at the repo root. If the `docs/briefs/` directory does not exist, create it first before writing the file. +**Say:** "A brief already exists at `docs/briefs/{project-name}.md` — overwrite, create a new version (e.g. `{project-name}-v2.md`), or pick a different name?" -After writing, confirm the path and tell the user: +Once path is confirmed, use `write`. If `docs/briefs/` does not exist, create it first. -**Say:** "Brief written to `docs/briefs/{project-name}.md`. Hand it to **Planning** when you're ready to break this into an exec-plan, or to **Orion** if the scope is already clear enough to start." +**Say:** "Brief written to `docs/briefs/{project-name}.md`. Hand it to **Planning** to break this into an exec-plan, or to **Orion** if scope is already clear enough to start." ## Language -Adapt to the user's language throughout the conversation — respond in French if they write in French, English if they write in English. Switch if they switch. - -If a message mixes languages, respond in the dominant language of the message, defaulting to English on a tie. - -If the user writes in a language other than FR or EN, respond in that language if possible; otherwise default to English and say: "I'll continue in English — let me know if you'd prefer French." - -The output brief is always written in English. +Respond in the user's language. The brief is always written in English. ## What Brainstorm Does NOT Do -- **No market research or competitive analysis** — you're here to clarify the problem and scope, not to assess the landscape. -- **No technical architecture or implementation decisions** — the how is Planning's and Orion's territory once the brief exists. -- **No task breakdown** — that's Planning's job once the brief is written. -- **No validation or critique of technology choices** — if the user has decided on a tech stack, record it as a Constraint and move on. - -## Permissions - -You operate with: -- `question` — to surface Tier 2 quality gate failures and structured clarifications -- `read` — to check for existing specs at session start and before writing, and to read project context -- `webfetch` — to gather context about external domains or systems the user references (context-gathering only) -- `write` — to write the output brief to `docs/briefs/{project-name}.md` -- `task` — to delegate codebase context exploration when the user references a project the agent hasn't read yet +- No market research or competitive analysis +- No technical architecture or implementation decisions +- No task breakdown (that's Planning's job) +- No validation or critique of technology choices — record stack choices as Constraints and move on +- No reading source files for reverse-engineering diff --git a/docs/briefs/.gitkeep b/docs/briefs/.gitkeep new file mode 100644 index 0000000..e69de29 diff --git a/docs/exec-plans/.gitkeep b/docs/exec-plans/.gitkeep new file mode 100644 index 0000000..e69de29 diff --git a/docs/guiding-principles.md b/docs/guiding-principles.md index 9306a61..5b2b046 100644 --- a/docs/guiding-principles.md +++ b/docs/guiding-principles.md @@ -122,3 +122,140 @@ const prompt = `You are Orion... **Threshold blocker:** A PR that moves agent prompt content into `index.js` as a string. Reject — extract to `agents/.md`. **Threshold warning:** An agent prompt file that exceeds 600 lines without a clear structural reason. Consider splitting into focused sections or extracting shared boilerplate to a separate file. + +--- + +## Principle: Agent prompt files do not declare permissions + +Permissions for every agent are declared exclusively in `index.js` via the `SUBAGENT_DEFS` array. An `agents/*.md` file must never contain a `## Permissions` section. Such a section is purely documentary — it has no effect on what the agent can actually do — and it diverges from the real enforcement in `index.js`. Stale or incorrect permission docs are worse than no docs. + +**Good:** +```markdown + +## Role + +You are a specialist agent that... + +## Workflow + +1. Receive task from orchestrator +2. ... +``` + +**Bad:** +```markdown + +## Permissions + +- task: allow +- todowrite: allow + +## Role + +You are a specialist agent that... +``` + +**Threshold blocker:** Any PR that adds a `## Permissions` section to any file under `agents/`. This is caught automatically by the `no-permissions-in-agent-prompts` CI check — do not merge until the section is removed. + +--- + +## Principle: Product briefs follow a verifiable schema + +Briefs produced by the brainstorm agent are consumed by downstream agents — Planning uses them to generate exec-plans, and Orion uses them to scope delegated work. A brief missing required frontmatter fields or section headings is not machine-actionable: a downstream agent cannot reliably extract the project name, scope, or success criteria without a predictable structure. The schema enforces the minimum structural contract. Content quality — whether the Vision is compelling, whether the Use Cases are realistic — remains the brainstorm agent's responsibility and is not checked here. + +**Good:** +```markdown +--- +project: "api-usage-dashboard" +type: tool +status: draft +created: 2026-04-03 +updated: 2026-04-03 +--- + +## Problem +... + +## Vision +... + +## Users +... + +## Core Use Cases +... + +## Success Criteria +... + +## Scope +... +``` + +**Bad:** +```markdown +--- +project: "api-usage-dashboard" +type: tool +status: draft +created: 2026-04-03 +--- + +## Problem +... + +## Vision +... + +## Users +... + +## Core Use Cases +... + +## Success Criteria +... +``` +*(Missing `updated:` frontmatter field and `## Scope` section — this brief would be rejected by CI.)* + +**Threshold blocker:** A brief file in `docs/briefs/` that is missing any of the 6 required sections (`## Problem`, `## Vision`, `## Users`, `## Core Use Cases`, `## Success Criteria`, `## Scope`) or any of the 5 required frontmatter fields (`project:`, `type:`, `status:`, `created:`, `updated:`). Caught automatically by the `brief-schema` CI check. + +**Threshold warning:** A brief with an `## Open Questions` or `## Rejected Ideas` section that is empty (no items) — indicates the brainstorm session may have been rushed. + +--- + +## Principle: Declared write/edit target directories must exist in the repo + +Every directory that an agent is granted `write` or `edit` access to in `index.js` must physically exist in the repository — either with a `.gitkeep` or real content. A missing directory causes a silent runtime failure: the agent has the correct permission configured but the underlying file operation fails with a misleading error (permissions conflict rather than "directory not found"). Without this check, a new agent permission can be declared and code-reviewed without anyone noticing the target directory was never created. + +**Good:** +```js +// In SUBAGENT_DEFS — write permission declared AND directory exists on disk +write: { + "*": "deny", + "docs/briefs/**": "allow", // docs/briefs/ exists (has .gitkeep or real files) +}, +``` +``` +docs/ + briefs/ + .gitkeep ← guarantees the directory is tracked by git +``` + +**Bad:** +```js +// Permission declared but directory absent from the repo +write: { + "*": "deny", + "docs/exec-plans/**": "allow", // docs/exec-plans/ does NOT exist → runtime failure +}, +``` +``` +docs/ + briefs/ + # exec-plans/ never created — agent silently fails at write time +``` + +**Threshold blocker:** Any PR that adds or modifies a `write` or `edit` permission path in `index.js` without a corresponding directory in the repository. Caught automatically by the `agent-write-dirs-exist` CI check — do not merge until the directory (with `.gitkeep`) is committed alongside the permission change. + +**Threshold warning:** A directory tracked only by `.gitkeep` that has accumulated real files — the `.gitkeep` can be removed, but is harmless if left in place. diff --git a/docs/specs/brainstorm-agent.md b/docs/specs/brainstorm-agent.md index 84e645f..03e1715 100644 --- a/docs/specs/brainstorm-agent.md +++ b/docs/specs/brainstorm-agent.md @@ -1,7 +1,7 @@ # Spec : Agent `brainstorm` -**Statut :** draft -**Mis à jour :** 2026-04-02 +**Statut :** implemented +**Mis à jour :** 2026-04-03 ## Résumé @@ -9,7 +9,7 @@ Spec de l'agent `brainstorm` — thinking partner de Phase 0. Aide à découvrir ## Rôle -Transformer une intention floue en product brief structuré, via un dialogue structuré en trois phases — sans jamais proposer de solutions prématurées. +Transformer une intention floue en product brief structuré, via un dialogue en trois phases — sans jamais proposer de solutions prématurées. > *"Clarifier le problème avant d'autoriser la solution."* @@ -24,40 +24,96 @@ Transformer une intention floue en product brief structuré, via un dialogue str ### Session Start -- Scan `docs/briefs/**/*.md` — détecter les drafts `status: draft` en cours -- Si draft trouvé : proposer de reprendre plutôt que de repartir à zéro -- Si nouveau brief : entrer en Phase 1 +- Delegate to an `explore` sub-agent: glob **all** `docs/briefs/**/*.md` (no status filter) +- **NONE found** → normal Phase 1 flow +- **ONE found** → read it, check its `status` field: + - `status: draft` → offer "continue editing or start fresh?" — CONTINUE jumps to Phase 3 revision mode + - Any other status (`done`, etc.) → offer "revise or new project?" — REVISE jumps to Phase 3 +- **MULTIPLE found** → list them, let the user pick one or confirm "new project" +- Si l'ouverture fournit déjà problème + scope : proposer de passer directement au draft +- Si l'utilisateur dit explicitement qu'il sait ce qu'il veut : sauter en Phase 3 ### Phase 1 — Discovery -- Poser des questions ouvertes : quel problème, qui est affecté, why now -- Identifier les hypothèses implicites -- Rechercher des patterns similaires existants (webfetch si pertinent) -- Ne pas proposer de solutions — poser des questions uniquement +- Ouvre toujours avec : "What problem are you trying to solve, and who experiences it?" +- Questions ouvertes sur le problème uniquement — jamais sur la solution +- Capture silencieuse des détails d'implémentation si l'utilisateur les donne (→ Constraints) +- Max 2 questions à la fois +- **Socratic pressure (légère)** : si l'utilisateur affirme un fait → demander une fois "What makes you confident about that?" — max une fois par hypothèse, jamais répété + +End Phase 1 : peut formuler le problème en 2–4 phrases sans mentionner de solution ou de technologie, et peut nommer l'utilisateur primaire par rôle et contexte. ### Phase 2 — Deep Dive -- Creuser les réponses : use cases, edge cases, contraintes, alternatives rejetées -- Clarifier les critères de succès -- Identifier les risques et inconnues -- Reformuler pour valider la compréhension +- Couvrir dans n'importe quel ordre : Scope, Success Criteria, Core Use Cases, Constraints, Rejected Ideas +- Pousser sur les critères de succès mesurables et orientés utilisateur +- **Socratic pressure (explicite)** : + - "Who said that was true?" + - "Why hasn't this been solved already?" + - "What are users doing today instead — and why would they switch?" + - "What's the fastest way this fails?" +- **Constraint reality check** : pour chaque contrainte énoncée → demander une fois "Is this a real constraint or an assumption — what breaks if this changes?" Accepter la réponse, ne jamais répéter +- `webfetch` si besoin de contexte sur un domaine ou système externe — résumer en Constraints, ne pas reproduire verbatim + +- **Early name check** : as soon as a project name crystallizes, check if `docs/briefs/{name}.md` already exists — if so, surface the conflict immediately (overwrite / new version / different name). Prevents discovering the conflict only at Phase 3 after a full session. + +End Phase 2 : peut remplir chaque section non-optionnelle du template. + +### Adversarial Gate (obligatoire avant Phase 3) + +Séquence en deux étapes, exécutée exactement une fois : + +1. Synthétiser le meilleur argument contre la construction du projet — "Here's the best case against: [1–2 sentences]. Does this change anything?" +2. Demander : "What would have to be true for this to fail in the first year?" — réponse enregistrée en Open Questions ou Constraints + +**Hard stop :** max 2 challenges adversariaux sur le même point. Après 2 challenges sans changement de position : accepter, enregistrer comme Open Question avec note "challenged twice, user held position", et continuer. ### Phase 3 — Draft + Validation -- Quality Gate avant écriture : - - Tier 1 (auto-fix silencieux) : incohérences mineures, gaps évidents - - Tier 2 (user input via `question`) : scope flou, critères de succès manquants, use case principal incertain -- Après validation : écrire dans `docs/briefs/{project-name}.md` -- Si le fichier existe déjà (`status: draft`) : proposer de continuer/mettre à jour plutôt que d'écraser +1. Générer le brief complet depuis le template +2. Présenter inline — ne pas écrire le fichier encore +3. Itérer sur les corrections jusqu'à confirmation +4. Annoncer le quality gate, l'exécuter, puis écrire le fichier + +**Fast-path** : si l'utilisateur a ouvert avec "I know exactly what I want, just help me write it up" — drafter depuis ce qu'il donne, présenter, itérer. Surfacer les gaps (out-of-scope manquant, critères vagues) en remplissant le template. Quality gate s'applique en intégralité. + +**Convergence rule** : +- Désaccord **cosmétique** (ton, formulation, ordre) → écrire le brief + note en Open Questions +- Désaccord **substantiel** (problème flou, utilisateurs non définis, pas de critères de succès) → STOP. "I won't write the brief until we resolve [X]." — "ship with open questions" n'est pas proposé comme échappatoire ### Règles comportementales | Situation | Action | |-----------|--------| -| Utilisateur veut aller directement à la solution | Rediriger vers la clarification du problème | -| Le brief commence à ressembler à un PRD détaillé | Stopper, simplifier | -| ≥ 3 rounds de Q&R sans convergence | Proposer d'écrire un draft partiel avec open questions | -| Brief en bonne forme | Écrire sans demander de permission supplémentaire | +| Critères de succès vagues | Refléter : "Fast compared to what? What does a user observe?" | +| Idée rejetée sans rationale | Demander une fois. Si refus : enregistrer `[rationale unknown]` | +| Conversation qui stagne | Lead avec une hypothèse remplie, pas une question vide | +| 3e question sans attendre réponse | Stopper — choisir les 2 plus importantes | +| Out-of-scope fourni | Enregistrer chaque item, même les obvieux | +| Scope In atteint 5+ items (check non encore fait) | Dire une fois : "This scope looks like 3–6 months of work — is that intentional, or should we trim?" — ne jamais relever à nouveau | + +## Quality Gate + +Exécuté avant d'écrire le fichier. + +### Tier 1 — Auto-fix (silencieux) + +- Solution language en Problem → réécrire en pain statement +- Vision cadrée comme feature → réécrire en outcome +- Vision > 3 phrases → condenser +- Project name non kebab-case → convertir +- Dates `created`/`updated` manquantes → remplir avec la date du jour +- Sections optionnelles vides → placeholder ou omission + +### Tier 2 — User input requis (`question`) + +- Utilisateur primaire non spécifique ("developers", "users") → demander rôle et contexte +- Use case sans acceptance criteria → demander l'observable result +- Critère de succès non mesurable ou non user-facing → demander la preuve observable +- Rejected Ideas avec `[rationale unknown]` → demander une fois, accepter si confirmation +- **Problem section absente → STOP** +- **Pas de success criteria → STOP** +- **Scope In vide → STOP** ## Artefact produit @@ -65,18 +121,16 @@ Transformer une intention floue en product brief structuré, via un dialogue str |------|--------|-------| | Product brief | `docs/briefs/{project-name}.md` | Input pour `planning` | -**Template :** +**YAML frontmatter :** `project`, `type`, `status`, `created`, `updated` -```yaml ---- -status: draft -created: {date} ---- -``` +**Sections :** Problem, Vision, Users, Core Use Cases, Success Criteria, Scope (In / Out), Constraints, Open Questions, Rejected Ideas -Sections : Problem, Vision, Users, Use Cases, Success Criteria, Scope (In / Out), Constraints, Open Questions, Rejected Ideas +**Langue :** conversation dans la langue de l'utilisateur — brief toujours écrit en anglais. -**Langue :** conversation en FR ou EN selon l'utilisateur — brief toujours écrit en anglais. +**Écriture du fichier :** +- Vérifier si `docs/briefs/{project-name}.md` existe déjà avant d'écrire +- Si existant : proposer d'écraser, créer `{project-name}-v2.md`, ou choisir un autre nom +- Créer `docs/briefs/` si absent ## Ce que l'agent ne fait PAS @@ -85,17 +139,7 @@ Sections : Problem, Vision, Users, Use Cases, Success Criteria, Scope (In / Out) - Ne prend pas de décisions architecturales - Ne lit pas les fichiers source du projet (pas de reverse-engineering) - Ne génère pas de tickets ou user stories - -## Permissions - -| Ressource | Accès | -|-----------|-------| -| `task` | allow | -| `question` | allow | -| `webfetch` | allow | -| `read` | allow — tous fichiers | -| `write` `docs/briefs/**` | allow | -| `write` reste du projet | deny | +- Ne fait pas de market research ni d'analyse concurrentielle ## Config diff --git a/index.js b/index.js index 296655e..5c755a2 100644 --- a/index.js +++ b/index.js @@ -312,6 +312,10 @@ const SUBAGENT_DEFS = [ "*": "deny", "docs/briefs/**": "allow", }, + edit: { + "*": "deny", + "docs/briefs/**": "allow", + }, }, }, ]; diff --git a/orion-docs/bundle.html b/orion-docs/bundle.html index 5485da8..e16326b 100644 --- a/orion-docs/bundle.html +++ b/orion-docs/bundle.html @@ -1,9 +1,23 @@ -orion-docs -
- - - + + + + + + + orion-docs + + + + +
+ + diff --git a/orion-docs/package.json b/orion-docs/package.json index 3fad3b0..7f6b76d 100644 --- a/orion-docs/package.json +++ b/orion-docs/package.json @@ -5,7 +5,7 @@ "type": "module", "scripts": { "dev": "vite", - "build": "tsc -b && vite build", + "build": "tsc -b && vite build && html-inline -i dist/index.html -b dist -o bundle.html", "lint": "eslint .", "preview": "vite preview" }, diff --git a/orion-docs/src/App.tsx b/orion-docs/src/App.tsx index f2d568e..53365fd 100644 --- a/orion-docs/src/App.tsx +++ b/orion-docs/src/App.tsx @@ -287,7 +287,23 @@ function SectionOverview() {
👤 Utilisateur
- + + {/* Phase 0 — brainstorm (upstream, before Orion) */} +
+
↓ si découverte produit
+
+
+
+ ◈ brainstorm (Phase 0) +
+
+
+
↓ produit docs/briefs/*.md
+
+
+
↓ sinon demande directe
+
+ {/* Orion center */}
@@ -585,21 +601,22 @@ function SectionPhases() { } function SectionFlows() { - const [active, setActive] = useState<"delivery" | "bug" | "maintenance">( - "delivery" - ); + const [active, setActive] = useState< + "delivery" | "bug" | "maintenance" | "discovery" + >("discovery"); return (
- Les 3 flux principaux + Les flux principaux - Selon la nature de la demande, Orion suit un flux différent. Le flux est - déterminé lors de la phase Comprendre. + Selon la nature de la demande, Orion (ou Brainstorm en Phase 0) suit un + flux différent. Le flux Orion est déterminé lors de la phase Comprendre. -
+
{( [ + { id: "discovery", label: "Phase 0 — Découverte" }, { id: "delivery", label: "Livraison (Feature)" }, { id: "bug", label: "Bug" }, { id: "maintenance", label: "Maintenance" }, @@ -619,6 +636,152 @@ function SectionFlows() { ))}
+ {active === "discovery" && ( +
+

Flux Phase 0 — Découverte produit (Brainstorm)

+

+ Le brainstorm s'exécute avant{" "} + Orion et Planning. Il transforme une idée floue en product brief + structuré via un dialogue Socratique en 3 phases. +

+
+
+ 👤 User → brainstorm agent + + + {/* Démarrage de session block */} +
+
+ Démarrage de session — explorer docs/briefs/ +
+
+
+
Aucun brief
+
→ Phase 1
+
+
+
Draft existant
+
continuer / nouveau
+
+
+
Brief terminé
+
réviser / nouveau
+
+
+
Multiples
+
liste → user choisit
+
+
+
+ + + + {/* Phase 1 */} +
+
+ + Phase 1 + + + Découverte + +
+
    +
  • ≤ 2 questions à la fois
    • +
  • Fin : problème en 2-4 phrases, utilisateur principal nommé
    • +
+
+ + + + {/* Phase 2 */} +
+
+ + Phase 2 + + + Approfondissement + +
+
    +
  • Scope, Critères de succès, Cas d'usage, Contraintes, Idées rejetées
    • +
  • 4 questions de défi
    • +
  • webfetch autorisé pour contexte domaine externe
    • +
+
+ + + + {/* Vérification adversariale */} +
+
+ Vérification adversariale +
+
    +
  1. + "Voici le meilleur argument contre ce projet…" → 3 choix proposés +
    2. +
  2. + "Qu'est-ce qui devrait être vrai pour que ça échoue en 1 an ?" + → enregistré en Open Questions / Contraintes +
    3. +
+

+ Séquentiel, obligatoire, exécuté une seule fois. +

+
+ + + + {/* Phase 3 */} +
+
+ + Phase 3 + + + Rédaction + Validation + +
+
    +
  • Générer le brief complet → présenter inline (pas d'écriture)
    • +
  • Itérer via question → Quality Gate
    • +
+
+ + + + {/* Quality Gate */} +
+
+ Quality Gate +
+
+
+
Tier 1 — auto-fix
+
Solution dans Problème, Vision >3 phrases, nom non kebab-case…
+
+
+
Tier 2 — question obligatoire
+
Utilisateur vague, Cas sans AC, Critère non mesurable…
+
+ STOP si bloquant (Problème absent, Scope In vide…)
+
+
+
+ + + Écrire docs/briefs/{nom}.md + +
+ → planning agent + → Orion +
+
+
+
+ )} + {active === "delivery" && (

Flux Livraison (Feature)

@@ -857,6 +1020,160 @@ function SectionAgents() { nécessaire, et des conditions d'activation explicites. + +
+
+
+ Démarrage de session +
+
    +
  • + › + Délègue explore docs/briefs/ en premier +
    • +
  • + › + Aucun brief → Phase 1 directement +
    • +
  • + › + Draft trouvé → continuer ou nouveau brief +
    • +
  • + › + Brief terminé → réviser ou nouveau +
    • +
  • + › + Multiples → liste, l'utilisateur choisit +
    • +
+

+ La lecture de fichiers est déléguée à un sous-agent{" "} + explore via task. +

+
+
+
+ Workflow 3 phases +
+
+
+ Phase 1 + + Découverte — ≤ 2 questions, problème en 2-4 phrases + +
+
+ Phase 2 + + Approfondissement — Scope, Critères, Cas d'usage, Contraintes + +
+
+ Phase 3 + + Rédaction + Validation — brief inline → Quality Gate → écriture fichier + +
+
+
+
+ +
+
+ Vérification adversariale (entre Phase 2 et Phase 3) +
+
    +
  1. + "Voici le meilleur argument contre ce projet…" → 3 choix proposés à l'utilisateur +
    2. +
  2. + "Qu'est-ce qui devrait être vrai pour que ça échoue en 1 an ?" → + enregistré en Open Questions / Contraintes +
    3. +
+

+ Séquentielle, obligatoire, exécutée une seule fois avant la Phase 3. +

+
+ +
+
+ Quality Gate +
+
+ Tier 1 — auto-fix silencieux + Tier 2 — question obligatoire + Tier 2 — STOP si bloquant +
+
    +
  • + › + Questions (Tier 2) : utilisateur vague, cas sans AC, critère non mesurable, rationale inconnu +
    • +
  • + › + STOP conditions : Problème absent, aucun critère de succès, Scope In vide +
    • +
+
+ +
+
+ Artefact de sortie +
+
+
# docs/briefs/{project-name}.md
+
---
+
project: nom-en-kebab-case
+
type: product # product | tool | library | service | experiment
+
status: draft | done
+
created / updated: date
+
---
+
## Problem
+
## Vision
+
## Users (Primary / Secondary)
+
## Core Use Cases (UC-NNN)
+
## Success Criteria (SC-NNN)
+
## Scope (In / Out)
+
## Constraints
+
## Open Questions
+
## Rejected Ideas
+
+
+ Phase 0 — s'exécute avant Orion et avant le planning agent. + Ne fait PAS : market research, architecture technique, tickets, backlog. +
+
+ Le brief est toujours rédigé en anglais, quelle que soit la langue de la session. +
+
+
+ } + /> + - - ("overview"); - const sectionComponents: Record = { - overview: , - phases: , - flows: , - agents: , - memory: , - "harness-gardener": , - protocols: , + const renderSection = () => { + switch (activeSection) { + case "overview": return ; + case "phases": return ; + case "flows": return ; + case "agents": return ; + case "memory": return ; + case "harness-gardener": return ; + case "protocols": return ; + } }; return ( @@ -1808,7 +2113,7 @@ export default function App() { {/* Main content */}
- {sectionComponents[activeSection]} + {renderSection()}
diff --git a/orion-docs/src/components/ui/resizable.tsx b/orion-docs/src/components/ui/resizable.tsx index cd3cb0e..8ed392b 100644 --- a/orion-docs/src/components/ui/resizable.tsx +++ b/orion-docs/src/components/ui/resizable.tsx @@ -6,8 +6,8 @@ import { cn } from "@/lib/utils" const ResizablePanelGroup = ({ className, ...props -}: React.ComponentProps) => ( - ) => ( + & { +}: React.ComponentProps & { withHandle?: boolean }) => ( - div]:rotate-90", className @@ -37,7 +37,7 @@ const ResizableHandle = ({
)} - + ) export { ResizablePanelGroup, ResizablePanel, ResizableHandle } diff --git a/team-lead-workflow/bundle.html b/team-lead-workflow/bundle.html index 46fbdde..ca39842 100644 --- a/team-lead-workflow/bundle.html +++ b/team-lead-workflow/bundle.html @@ -1,6 +1,18 @@ -team-lead-workflow -
- - - +}`;function De({code:e}){return(0,b.jsx)(`pre`,{style:{background:`#0f172a`,color:`#e2e8f0`,borderRadius:8,padding:`18px 20px`,fontSize:13,lineHeight:1.65,fontFamily:`ui-monospace, 'Cascadia Code', monospace`,overflowX:`auto`,margin:0},children:e.split(` +`).map((e,t)=>{let n=e.replace(/("(?:[^"\\]|\\.)*")(\s*:)/g,`$1$2`).replace(/:\s*("(?:[^"\\]|\\.)*")/g,`: $1`).replace(/:\s*(true|false|null)/g,`: $1`).replace(/:\s*(-?\d+(?:\.\d+)?)/g,`: $1`).split(/(|<\/k>||<\/s>||<\/b>||<\/n>)/),r=``,i=[];return n.forEach((e,t)=>{if(e===``){r=`k`;return}if(e===``){r=``;return}if(e===``){r=`s`;return}if(e===``){r=``;return}if(e===``){r=`b`;return}if(e===``){r=``;return}if(e===``){r=`n`;return}if(e===``){r=``;return}if(!e)return;let n=r===`k`?`#93c5fd`:r===`s`?`#86efac`:r===`b`||r===`n`?`#fcd34d`:`#e2e8f0`;i.push((0,b.jsx)(`span`,{style:{color:n},children:e},t))}),(0,b.jsx)(`div`,{children:i},t)})})}function Oe({fields:e,t}){return(0,b.jsx)(`div`,{style:{overflowX:`auto`},children:(0,b.jsxs)(`table`,{style:{width:`100%`,borderCollapse:`collapse`,fontSize:13,fontFamily:`system-ui, sans-serif`},children:[(0,b.jsx)(`thead`,{children:(0,b.jsx)(`tr`,{style:{borderBottom:`2px solid #e2e8f0`},children:[t.col_field,t.col_type,t.col_default,t.col_description].map(e=>(0,b.jsx)(`th`,{style:{textAlign:`left`,padding:`8px 12px`,fontSize:11,fontWeight:700,textTransform:`uppercase`,letterSpacing:`0.08em`,color:`#94a3b8`},children:e},e))})}),(0,b.jsx)(`tbody`,{children:e.map((e,t)=>(0,b.jsxs)(`tr`,{style:{borderBottom:`1px solid #f1f5f9`,background:t%2==0?`white`:`#fafafa`},children:[(0,b.jsx)(`td`,{style:{padding:`9px 12px`},children:(0,b.jsx)(`code`,{style:{background:`#f1f5f9`,color:`#0f172a`,padding:`2px 7px`,borderRadius:4,fontSize:12,fontFamily:`ui-monospace, monospace`},children:e.field})}),(0,b.jsx)(`td`,{style:{padding:`9px 12px`,color:`#7c3aed`,fontFamily:`ui-monospace, monospace`,fontSize:12},children:e.type}),(0,b.jsx)(`td`,{style:{padding:`9px 12px`,color:`#64748b`,fontFamily:`ui-monospace, monospace`,fontSize:12},children:e.default}),(0,b.jsx)(`td`,{style:{padding:`9px 12px`,color:`#374151`,lineHeight:1.5},children:e.description})]},t))})]})})}function ke({agent:e,t}){let[n,r]=(0,_.useState)(!1),i={error:`#dc2626`,warning:`#d97706`,info:`#0369a1`,success:`#16a34a`},a={error:`#fef2f2`,warning:`#fffbeb`,info:`#eff6ff`,success:`#f0fdf4`},o=i[e.color]??`#64748b`,s=a[e.color]??`#f8fafc`;return(0,b.jsxs)(`div`,{style:{border:`1px solid #e2e8f0`,borderRadius:10,overflow:`hidden`,marginBottom:10},children:[(0,b.jsxs)(`div`,{style:{display:`flex`,alignItems:`center`,justifyContent:`space-between`,padding:`12px 16px`,background:`white`},children:[(0,b.jsxs)(`div`,{style:{display:`flex`,alignItems:`center`,gap:12},children:[(0,b.jsx)(`code`,{style:{fontSize:14,fontWeight:700,color:`#0f172a`,fontFamily:`ui-monospace, monospace`,background:`#f1f5f9`,padding:`2px 8px`,borderRadius:4},children:e.name}),(0,b.jsx)(`span`,{style:{fontSize:10,fontWeight:700,letterSpacing:`0.1em`,color:o,background:s,border:`1px solid ${o}30`,padding:`2px 7px`,borderRadius:3},children:e.color.toUpperCase()})]}),(0,b.jsxs)(`div`,{style:{display:`flex`,alignItems:`center`,gap:20},children:[(0,b.jsx)(`div`,{style:{display:`flex`,gap:14},children:[{label:t.col_temp,value:e.temperature},{label:t.col_variant,value:e.variant},{label:t.col_mode,value:e.mode}].map(e=>(0,b.jsxs)(`div`,{style:{textAlign:`center`},children:[(0,b.jsx)(`div`,{style:{fontSize:10,color:`#94a3b8`,fontWeight:600,textTransform:`uppercase`,letterSpacing:`0.06em`},children:e.label}),(0,b.jsx)(`div`,{style:{fontSize:12,color:`#0f172a`,fontWeight:700,fontFamily:`ui-monospace, monospace`},children:e.value})]},e.label))}),(0,b.jsx)(`button`,{onClick:()=>r(e=>!e),style:{background:`#f8fafc`,border:`1px solid #e2e8f0`,borderRadius:5,padding:`4px 10px`,cursor:`pointer`,fontSize:12,color:`#64748b`,fontWeight:600,fontFamily:`system-ui, sans-serif`},children:n?t.config_defaults_collapse:t.config_defaults_expand})]})]}),n&&(0,b.jsxs)(`div`,{style:{background:`#f8fafc`,borderTop:`1px solid #e2e8f0`,padding:`12px 16px`},children:[(0,b.jsx)(`div`,{style:{fontSize:11,fontWeight:700,textTransform:`uppercase`,letterSpacing:`0.08em`,color:`#94a3b8`,marginBottom:8},children:t.col_permissions}),(0,b.jsx)(`div`,{style:{display:`flex`,flexDirection:`column`,gap:4},children:e.permissions.map((e,t)=>{let n=e.toLowerCase().includes(`deny`)||e.toLowerCase().includes(`tout le reste`);return(0,b.jsxs)(`div`,{style:{display:`flex`,alignItems:`center`,gap:8},children:[(0,b.jsx)(`span`,{style:{width:6,height:6,borderRadius:`50%`,flexShrink:0,background:n?`#dc262640`:`#16a34a40`,border:`1.5px solid ${n?`#dc2626`:`#16a34a`}`}}),(0,b.jsx)(`span`,{style:{fontSize:12,color:n?`#991b1b`:`#374151`,fontFamily:`ui-monospace, monospace`},children:e})]},t)})})]})]})}function Ae({onBack:e,onWorkflow:t,lang:n,setLang:r}){let i=Se[n];return(0,b.jsxs)(`div`,{style:{height:`100vh`,width:`100vw`,overflowY:`auto`,fontFamily:`system-ui, 'Segoe UI', sans-serif`,background:`#f8f9fa`,animation:`fadeIn 0.25s ease-out`},children:[(0,b.jsxs)(`div`,{style:{background:`white`,borderBottom:`1px solid #e2e8f0`,padding:`10px 24px`,position:`sticky`,top:0,zIndex:10,display:`flex`,alignItems:`center`,justifyContent:`space-between`},children:[(0,b.jsxs)(`div`,{style:{display:`flex`,alignItems:`center`,gap:12},children:[(0,b.jsx)(`button`,{onClick:e,style:{background:`none`,border:`none`,cursor:`pointer`,fontSize:12,color:`#64748b`,fontWeight:600,padding:`4px 8px`,borderRadius:5,fontFamily:`system-ui, sans-serif`},onMouseEnter:e=>{e.currentTarget.style.background=`#f1f5f9`},onMouseLeave:e=>{e.currentTarget.style.background=`none`},children:i.back_to_intro}),(0,b.jsx)(`div`,{style:{width:1,height:16,background:`#e2e8f0`}}),(0,b.jsx)(`button`,{onClick:t,style:{background:`none`,border:`none`,cursor:`pointer`,fontSize:12,color:`#64748b`,fontWeight:600,padding:`4px 8px`,borderRadius:5,fontFamily:`system-ui, sans-serif`},onMouseEnter:e=>{e.currentTarget.style.background=`#f1f5f9`},onMouseLeave:e=>{e.currentTarget.style.background=`none`},children:i.nav_workflow}),(0,b.jsx)(`div`,{style:{width:1,height:16,background:`#e2e8f0`}}),(0,b.jsxs)(`span`,{style:{fontSize:14,fontWeight:700,color:`#0f172a`},children:[`team-lead — `,i.config_title]}),(0,b.jsx)(`span`,{style:{fontSize:12,color:`#94a3b8`},children:i.config_subtitle})]}),(0,b.jsx)(Ce,{lang:n,setLang:r})]}),(0,b.jsxs)(`div`,{style:{maxWidth:860,margin:`0 auto`,padding:`36px 48px 72px`},children:[(0,b.jsxs)(`section`,{style:{marginBottom:40},children:[(0,b.jsx)(z,{children:i.config_intro_heading}),(0,b.jsx)(`div`,{style:{background:`white`,border:`1px solid #e2e8f0`,borderRadius:10,padding:`18px 22px`},children:(0,b.jsx)(`p`,{style:{margin:0,fontSize:14,color:`#374151`,lineHeight:1.7},children:i.config_intro_body.split(`prompt`).map((e,t,n)=>t(0,b.jsx)(ke,{agent:e,t:i},e.name))]}),(0,b.jsxs)(`section`,{style:{marginBottom:40},children:[(0,b.jsx)(z,{children:i.config_example_heading}),(0,b.jsx)(`div`,{style:{borderRadius:10,overflow:`hidden`,border:`1px solid #1e293b`},children:(0,b.jsx)(De,{code:Ee})}),(0,b.jsxs)(`div`,{style:{marginTop:10,background:`#f0fdf4`,border:`1px solid #bbf7d0`,borderRadius:7,padding:`10px 14px`,display:`flex`,gap:10,alignItems:`flex-start`},children:[(0,b.jsx)(`span`,{style:{fontSize:14,flexShrink:0,marginTop:1},children:`✓`}),(0,b.jsx)(`span`,{style:{fontSize:13,color:`#166534`,lineHeight:1.6},children:i.config_example_note})]})]}),(0,b.jsxs)(`section`,{style:{marginBottom:40},children:[(0,b.jsx)(z,{children:i.config_limits_heading}),(0,b.jsx)(`div`,{style:{background:`white`,border:`1px solid #e2e8f0`,borderRadius:10,padding:`16px 20px`},children:i.config_limits.map((e,t)=>(0,b.jsxs)(`div`,{style:{display:`flex`,alignItems:`flex-start`,gap:10,marginBottom:ts(e=>Math.min(2,Math.round((e+.1)*10)/10)),f=()=>s(e=>Math.max(.5,Math.round((e-.1)*10)/10)),p=()=>s(1),m=(e,t)=>{a(e);let n=u.current;if(n){let e=t*o-n.clientHeight/2;n.scrollTo({top:Math.max(0,e),behavior:`smooth`})}},h=e=>{l(e),a(e===`orion`?`understand`:`bs_start`),s(1);let t=u.current;t&&t.scrollTo({top:0,behavior:`smooth`})},g=Se[n];return e===`intro`?(0,b.jsxs)(b.Fragment,{children:[(0,b.jsx)(`style`,{children:x}),(0,b.jsx)(we,{onEnter:()=>t(`flowchart`),onConfig:()=>t(`config`),lang:n,setLang:r})]}):e===`config`?(0,b.jsxs)(b.Fragment,{children:[(0,b.jsx)(`style`,{children:x}),(0,b.jsx)(Ae,{onBack:()=>t(`intro`),onWorkflow:()=>t(`flowchart`),lang:n,setLang:r})]}):(0,b.jsxs)(b.Fragment,{children:[(0,b.jsx)(`style`,{children:x}),(0,b.jsxs)(`div`,{style:{display:`flex`,flexDirection:`column`,height:`100vh`,width:`100vw`,background:`#f8f9fa`,fontFamily:`system-ui, 'Segoe UI', sans-serif`,overflow:`hidden`,animation:`fadeIn 0.25s ease-out`},children:[(0,b.jsxs)(`div`,{style:{background:`white`,borderBottom:`1px solid #e2e8f0`,padding:`10px 20px`,flexShrink:0,display:`flex`,alignItems:`center`,justifyContent:`space-between`},children:[(0,b.jsxs)(`div`,{style:{display:`flex`,alignItems:`center`,gap:12},children:[(0,b.jsx)(`button`,{onClick:()=>t(`intro`),style:{background:`none`,border:`none`,cursor:`pointer`,fontSize:12,color:`#64748b`,fontWeight:600,display:`flex`,alignItems:`center`,gap:4,padding:`4px 8px`,borderRadius:5,fontFamily:`system-ui, sans-serif`},onMouseEnter:e=>{e.currentTarget.style.background=`#f1f5f9`},onMouseLeave:e=>{e.currentTarget.style.background=`none`},children:g.back_to_intro}),(0,b.jsx)(`div`,{style:{width:1,height:16,background:`#e2e8f0`}}),(0,b.jsx)(`button`,{onClick:()=>t(`config`),style:{background:`none`,border:`none`,cursor:`pointer`,fontSize:12,color:`#64748b`,fontWeight:600,padding:`4px 8px`,borderRadius:5,fontFamily:`system-ui, sans-serif`},onMouseEnter:e=>{e.currentTarget.style.background=`#f1f5f9`},onMouseLeave:e=>{e.currentTarget.style.background=`none`},children:g.nav_config}),(0,b.jsx)(`div`,{style:{width:1,height:16,background:`#e2e8f0`}}),(0,b.jsx)(`div`,{style:{display:`flex`,alignItems:`center`,gap:2,background:`#f1f5f9`,borderRadius:8,padding:`3px`},children:[{key:`orion`,label:g.tab_orion,activeColor:`#4f46e5`,activeBg:`white`},{key:`brainstorm`,label:g.tab_brainstorm,activeColor:`#6d28d9`,activeBg:`white`}].map(e=>(0,b.jsx)(`button`,{onClick:()=>h(e.key),style:{background:c===e.key?e.activeBg:`none`,border:`none`,borderRadius:6,cursor:`pointer`,fontSize:12,fontWeight:c===e.key?700:500,color:c===e.key?e.activeColor:`#64748b`,padding:`4px 12px`,fontFamily:`system-ui, sans-serif`,boxShadow:c===e.key?`0 1px 3px rgba(0,0,0,0.1)`:`none`,transition:`all 0.15s`,whiteSpace:`nowrap`},children:e.label},e.key))})]}),(0,b.jsxs)(`div`,{style:{display:`flex`,alignItems:`center`,gap:16},children:[(0,b.jsx)(Ce,{lang:n,setLang:r}),(0,b.jsx)(`span`,{style:{fontSize:11,color:`#cbd5e1`,fontStyle:`italic`},children:g.click_node_hint})]})]}),(0,b.jsxs)(`div`,{style:{flex:1,display:`flex`,overflow:`hidden`},children:[(0,b.jsxs)(`div`,{id:`flowchart-container`,ref:u,style:{width:`45%`,minWidth:320,background:`#f8f9fa`,borderRight:`1px solid #e2e8f0`,overflowY:`auto`,overflowX:`hidden`,display:`flex`,flexDirection:`column`,alignItems:`center`,position:`relative`},children:[(0,b.jsxs)(`div`,{style:{position:`sticky`,top:10,zIndex:10,alignSelf:`flex-start`,marginLeft:10,display:`flex`,alignItems:`center`,gap:4,background:`white`,border:`1px solid #e2e8f0`,borderRadius:8,padding:`4px 8px`,boxShadow:`0 1px 4px rgba(0,0,0,0.08)`},children:[(0,b.jsx)(`button`,{onClick:f,style:{background:`#f1f5f9`,border:`none`,borderRadius:5,width:26,height:26,cursor:`pointer`,fontSize:14,color:`#475569`,fontWeight:700,display:`flex`,alignItems:`center`,justifyContent:`center`},children:`−`}),(0,b.jsxs)(`span`,{style:{fontSize:12,color:`#64748b`,fontWeight:600,minWidth:36,textAlign:`center`,fontFamily:`system-ui, sans-serif`},children:[Math.round(o*100),`%`]}),(0,b.jsx)(`button`,{onClick:d,style:{background:`#f1f5f9`,border:`none`,borderRadius:5,width:26,height:26,cursor:`pointer`,fontSize:14,color:`#475569`,fontWeight:700,display:`flex`,alignItems:`center`,justifyContent:`center`},children:`+`}),(0,b.jsx)(`button`,{onClick:p,style:{background:`#f1f5f9`,border:`none`,borderRadius:5,width:26,height:26,cursor:`pointer`,fontSize:13,color:`#475569`,display:`flex`,alignItems:`center`,justifyContent:`center`},children:`↺`})]}),(0,b.jsx)(`div`,{style:{transformOrigin:`top center`,transform:`scale(${o})`,width:`fit-content`},children:c===`orion`?(0,b.jsx)(pe,{selected:i,onSelect:m,lang:n}):(0,b.jsx)(he,{selected:i,onSelect:m,lang:n})})]}),(0,b.jsx)(`div`,{style:{flex:1,background:`white`,overflowY:`auto`},children:(0,b.jsx)(xe,{nodeId:i,lang:n})})]})]})]})}(0,v.createRoot)(document.getElementById(`root`)).render((0,b.jsx)(_.StrictMode,{children:(0,b.jsx)(je,{})})); + + + +
+ + diff --git a/team-lead-workflow/src/App.tsx b/team-lead-workflow/src/App.tsx index ed383ac..5af8bbf 100644 --- a/team-lead-workflow/src/App.tsx +++ b/team-lead-workflow/src/App.tsx @@ -27,6 +27,50 @@ interface DetailData { // ─── Flowchart i18n data ────────────────────────────────────────────────────── +interface BrainstormSvgLabels { + bs_start: string; + bs_existing_check: string; + bs_single_found: string; + bs_multi_found: string; + bs_status_check: string; + bs_ask_continue: string; + bs_load_brief: string; + bs_phase1: string; + bs_problem_clear: string; + bs_phase2: string; + bs_adversarial: string; + bs_template_fillable: string; + bs_phase3: string; + bs_quality_gate: string; + bs_quality_passed: string; + bs_file_exists: string; + bs_file_conflict: string; + bs_write: string; + bs_end: string; + // arrow labels + bs_arrow_yes: string; + bs_arrow_no: string; + bs_arrow_one: string; + bs_arrow_multiple: string; + bs_arrow_none: string; + bs_arrow_draft: string; + bs_arrow_done: string; + bs_arrow_continue: string; + bs_arrow_fresh: string; + bs_arrow_choose: string; + bs_arrow_new: string; + bs_arrow_all_fillable: string; + bs_arrow_missing: string; + bs_arrow_passed: string; + bs_arrow_tier2: string; + bs_arrow_blocked: string; + bs_esc_blocked_label: string; + bs_esc_blocked_sub: string; + bs_arrow_overwrite: string; + bs_arrow_version: string; + bs_arrow_rename: string; +} + interface FlowchartData { svgLabels: { start: string; @@ -53,6 +97,8 @@ interface FlowchartData { annot_memory: string; }; details: Record; + brainstormSvgLabels: BrainstormSvgLabels; + brainstormDetails: Record; } function getFlowchartData(lang: "en" | "fr"): FlowchartData { @@ -332,6 +378,220 @@ function getFlowchartData(lang: "en" | "fr"): FlowchartData { ], }, }, + brainstormSvgLabels: { + bs_start: "Démarrage session", + bs_existing_check: "Briefs existants ?", + bs_single_found: "Un brief trouvé", + bs_multi_found: "Plusieurs trouvés", + bs_status_check: "Statut = brouillon ?", + bs_ask_continue: "Continuer ou nouveau ?", + bs_load_brief: "Charger le brief", + bs_phase1: "Phase 1 — Découverte", + bs_problem_clear: "Problème clair ?", + bs_phase2: "Phase 2 — Approfondissement", + bs_adversarial: "Porte adversariale", + bs_template_fillable: "Toutes sections remplissables ?", + bs_phase3: "Phase 3 — Rédaction + Validation", + bs_quality_gate: "Porte qualité", + bs_quality_passed: "Porte qualité passée ?", + bs_file_exists: "Fichier existant ?", + bs_file_conflict: "Écraser / v2 / renommer ?", + bs_write: "Écrire le brief", + bs_end: "Brief écrit. Passer à Planning ou Orion.", + bs_arrow_yes: "OUI", + bs_arrow_no: "NON", + bs_arrow_one: "UN SEUL", + bs_arrow_multiple: "PLUSIEURS", + bs_arrow_none: "AUCUN", + bs_arrow_draft: "BROUILLON", + bs_arrow_done: "TERMINÉ", + bs_arrow_continue: "CONTINUER", + bs_arrow_fresh: "NOUVEAU", + bs_arrow_choose: "CHOISIR EXISTANT", + bs_arrow_new: "NOUVEAU PROJET", + bs_arrow_all_fillable: "OUI", + bs_arrow_missing: "NON", + bs_arrow_passed: "PASSÉ", + bs_arrow_tier2: "NIVEAU 2", + bs_arrow_blocked: "BLOQUÉ", + bs_esc_blocked_label: "Escalade", + bs_esc_blocked_sub: "BLOQUÉ", + bs_arrow_overwrite: "ÉCRASER", + bs_arrow_version: "NOUVELLE VERSION", + bs_arrow_rename: "RENOMMER", + }, + brainstormDetails: { + bs_start: { + title: "Session Start", + color: "#0d9488", + nodeType: "ENTRY POINT", + sections: [ + { heading: "What happens", items: ["Session is initiated with brainstorm agent", "Agent globs docs/briefs/**/*.md to check for existing briefs", "Routing decision made before any questions are asked"] }, + ], + }, + bs_existing_check: { + title: "Existing briefs found?", + color: "#0d9488", + nodeType: "DECISION", + sections: [ + { heading: "Branches", items: ["NO → Flow normal → Phase 1 (Discovery)", "ONE found → check status (draft / done)", "MULTIPLE found → list briefs, ask which one or new project"] }, + ], + }, + bs_single_found: { + title: "One brief found", + color: "#0891b2", + nodeType: "ACTION", + sections: [ + { heading: "What happens", items: ["Single brief located at docs/briefs/", "Agent checks the status field in the brief frontmatter", "Routes to status decision"] }, + ], + }, + bs_multi_found: { + title: "Multiple briefs found", + color: "#0891b2", + nodeType: "ACTION", + sections: [ + { heading: "What happens", items: ["Agent lists all found briefs to the user", "Asks: which one to resume, or start a new project?", "CHOOSE EXISTING → Load brief → Phase 3 (revision)", "NEW PROJECT → Flow normal → Phase 1"] }, + ], + }, + bs_status_check: { + title: "Status = draft?", + color: "#0891b2", + nodeType: "DECISION", + sections: [ + { heading: "Branches", items: ["YES (draft) → Ask: continue or fresh start?", "NO (done/other) → Inform user, ask new project name → Phase 1"] }, + ], + }, + bs_ask_continue: { + title: "Continue or fresh start?", + color: "#0891b2", + nodeType: "ACTION", + sections: [ + { heading: "What happens", items: ["User is shown the existing draft brief summary", "Asked: resume from where we left off, or start fresh?", "CONTINUE → Load brief → jump directly to Phase 3 (revision)", "FRESH → Ignore existing brief → Phase 1 (Discovery)"] }, + ], + }, + bs_load_brief: { + title: "Load brief", + color: "#0891b2", + nodeType: "ACTION", + sections: [ + { heading: "What happens", items: ["Agent reads the existing brief file from docs/briefs/", "Provides full context to Phase 3 (revision mode)", "User can iterate on the existing content rather than restarting"] }, + ], + }, + bs_phase1: { + title: "Phase 1 — Discovery", + color: "#2563eb", + nodeType: "MAIN PHASE", + sections: [ + { heading: "Core question", items: ["\"What problem are you trying to solve, and who experiences it?\""] }, + { heading: "Rules", items: ["Max 2 questions at a time — never overwhelm", "Surface the problem, not the solution", "Do not accept vague answers — push for specifics", "Iterate until problem is stated clearly"] }, + { heading: "Exit criteria", items: ["Problem stated in 2–4 sentences", "Primary user named", "Problem is a problem, not a feature"] }, + ], + }, + bs_problem_clear: { + title: "Problem clear?", + color: "#2563eb", + nodeType: "DECISION", + sections: [ + { heading: "Exit criteria", items: ["YES → problem stated in 2–4 clear sentences AND primary user named → Phase 2", "NO → iterate — ask more targeted follow-up questions"] }, + ], + }, + bs_phase2: { + title: "Phase 2 — Deep Dive", + color: "#4f46e5", + nodeType: "MAIN PHASE", + sections: [ + { heading: "Topics to cover", items: ["Scope and boundaries — what is explicitly out of scope?", "Success criteria — how will you know it worked?", "Use cases — top 3–5 concrete scenarios", "Constraints — technical, time, team, budget", "Rejected ideas — what was considered and discarded?"] }, + { heading: "Socratic pressure", items: ["Challenge assumptions — \"Why is X the right approach?\"", "Ask about failure modes — \"What would make this fail?\"", "Probe edges — \"What happens when Y doesn't work?\""] }, + ], + }, + bs_adversarial: { + title: "Adversarial Gate", + color: "#7c3aed", + nodeType: "GATE", + sections: [ + { heading: "Two mandatory questions", items: ["\"What is the strongest case against building this?\"", "\"What would have to be true for this to fail in year 1?\""] }, + { heading: "Purpose", items: ["Forces the user to articulate real risks", "Prevents over-optimistic briefs that skip failure modes", "If user can't answer, the problem statement needs more work"] }, + ], + }, + bs_template_fillable: { + title: "All template sections fillable?", + color: "#7c3aed", + nodeType: "DECISION", + sections: [ + { heading: "Branches", items: ["YES → proceed to Phase 3 (draft + validation)", "NO → iterate back in Phase 2 — identify which sections are still empty"] }, + { heading: "Template sections required", items: ["Problem statement", "Primary user", "Success criteria", "Top use cases", "Constraints", "Out of scope", "Risks / adversarial answers"] }, + ], + }, + bs_phase3: { + title: "Phase 3 — Draft + Validation", + color: "#6d28d9", + nodeType: "MAIN PHASE", + sections: [ + { heading: "What happens", items: ["Agent generates the full brief inline from collected context", "User reviews the draft and provides feedback", "Agent iterates until user confirms the brief is ready", "Quality gate is run before writing to disk"] }, + { heading: "Output format", items: ["Markdown file at docs/briefs/{project-name}.md", "Structured sections: problem, users, success criteria, use cases, constraints, risks"] }, + ], + }, + bs_quality_gate: { + title: "Quality Gate", + color: "#6d28d9", + nodeType: "GATE", + sections: [ + { heading: "Tier 1 — auto-fix silently", items: ["Minor formatting issues", "Incomplete sentences that can be inferred", "Missing punctuation or capitalization"] }, + { heading: "Tier 2 — ask user via question tool", items: ["Ambiguous success criteria", "Conflicting constraints", "Vague scope boundaries"] }, + { heading: "BLOCKED — escalate immediately", items: ["No problem statement at all", "No success criteria", "Empty scope — can't determine what to build"] }, + ], + }, + bs_quality_passed: { + title: "Quality gate passed?", + color: "#6d28d9", + nodeType: "DECISION", + sections: [ + { heading: "Branches", items: ["PASSED → proceed to file write check", "TIER 2 issues → ask user → resolve → re-run gate", "BLOCKED (no problem, no success criteria, empty scope) → STOP — escalate to user, do not write"] }, + ], + }, + bs_file_exists: { + title: "File already exists?", + color: "#7c3aed", + nodeType: "DECISION", + sections: [ + { heading: "Check", items: ["Agent checks if docs/briefs/{project-name}.md already exists on disk"] }, + { heading: "Branches", items: ["NO → write directly", "YES → ask user: overwrite, new version, or rename?"] }, + ], + }, + bs_file_conflict: { + title: "Overwrite / new version / rename?", + color: "#7c3aed", + nodeType: "ACTION", + sections: [ + { heading: "Options", items: ["OVERWRITE → replace existing file with new brief", "NEW VERSION → write as {name}-v2.md (or -v3, etc.)", "RENAME → write with a custom filename provided by the user"] }, + ], + }, + bs_write: { + title: "Write file", + color: "#15803d", + nodeType: "ACTION", + sections: [ + { heading: "What happens", items: ["Agent writes the validated brief to docs/briefs/{project-name}.md", "File is created or overwritten depending on the conflict resolution choice", "Brief is ready for Planning or Orion to consume"] }, + ], + }, + bs_end: { + title: "Brief written", + color: "#1e293b", + nodeType: "DELIVERY", + sections: [ + { heading: "Handoff", items: ["Brief written to docs/briefs/{project-name}.md", "Hand to Planning agent for execution plan", "Or hand to Orion (team-lead) directly for implementation"] }, + ], + }, + bs_esc_blocked: { + title: "Escalation — BLOCKED", + color: "#991b1b", + nodeType: "ESCALATION", + sections: [ + { heading: "When this triggers", items: ["No problem statement at all", "No success criteria defined", "Scope is empty — cannot determine what to build"] }, + { heading: "What happens", items: ["Agent stops immediately — does not write the brief", "Reports precisely what is missing to the user", "User must provide the missing information before continuing"] }, + ], + }, + }, }; } @@ -611,12 +871,229 @@ function getFlowchartData(lang: "en" | "fr"): FlowchartData { ], }, }, + brainstormSvgLabels: { + bs_start: "Session Start", + bs_existing_check: "Existing briefs?", + bs_single_found: "One brief found", + bs_multi_found: "Multiple found", + bs_status_check: "Status = draft?", + bs_ask_continue: "Continue or fresh?", + bs_load_brief: "Load brief", + bs_phase1: "Phase 1 — Discovery", + bs_problem_clear: "Problem clear?", + bs_phase2: "Phase 2 — Deep Dive", + bs_adversarial: "Adversarial Gate", + bs_template_fillable: "All sections fillable?", + bs_phase3: "Phase 3 — Draft + Validate", + bs_quality_gate: "Quality Gate", + bs_quality_passed: "Quality gate passed?", + bs_file_exists: "File already exists?", + bs_file_conflict: "Overwrite / version / rename?", + bs_write: "Write file", + bs_end: "Brief written. Hand to Planning or Orion.", + bs_arrow_yes: "YES", + bs_arrow_no: "NO", + bs_arrow_one: "ONE", + bs_arrow_multiple: "MULTIPLE", + bs_arrow_none: "NONE", + bs_arrow_draft: "DRAFT", + bs_arrow_done: "DONE", + bs_arrow_continue: "CONTINUE", + bs_arrow_fresh: "FRESH", + bs_arrow_choose: "CHOOSE EXISTING", + bs_arrow_new: "NEW PROJECT", + bs_arrow_all_fillable: "YES", + bs_arrow_missing: "NO", + bs_arrow_passed: "PASSED", + bs_arrow_tier2: "TIER 2", + bs_arrow_blocked: "BLOCKED", + bs_esc_blocked_label: "Escalation", + bs_esc_blocked_sub: "BLOCKED", + bs_arrow_overwrite: "OVERWRITE", + bs_arrow_version: "NEW VERSION", + bs_arrow_rename: "RENAME", + }, + brainstormDetails: { + bs_start: { + title: "Session Start", + color: "#0d9488", + nodeType: "ENTRY POINT", + sections: [ + { heading: "What happens", items: ["Session is initiated with brainstorm agent", "Agent globs docs/briefs/**/*.md to check for existing briefs", "Routing decision made before any questions are asked"] }, + ], + }, + bs_existing_check: { + title: "Existing briefs found?", + color: "#0d9488", + nodeType: "DECISION", + sections: [ + { heading: "Branches", items: ["NO → Flow normal → Phase 1 (Discovery)", "ONE found → check status (draft / done)", "MULTIPLE found → list briefs, ask which one or new project"] }, + ], + }, + bs_single_found: { + title: "One brief found", + color: "#0891b2", + nodeType: "ACTION", + sections: [ + { heading: "What happens", items: ["Single brief located at docs/briefs/", "Agent checks the status field in the brief frontmatter", "Routes to status decision"] }, + ], + }, + bs_multi_found: { + title: "Multiple briefs found", + color: "#0891b2", + nodeType: "ACTION", + sections: [ + { heading: "What happens", items: ["Agent lists all found briefs to the user", "Asks: which one to resume, or start a new project?", "CHOOSE EXISTING → Load brief → Phase 3 (revision)", "NEW PROJECT → Flow normal → Phase 1"] }, + ], + }, + bs_status_check: { + title: "Status = draft?", + color: "#0891b2", + nodeType: "DECISION", + sections: [ + { heading: "Branches", items: ["YES (draft) → Ask: continue or fresh start?", "NO (done/other) → Inform user, ask new project name → Phase 1"] }, + ], + }, + bs_ask_continue: { + title: "Continue or fresh start?", + color: "#0891b2", + nodeType: "ACTION", + sections: [ + { heading: "What happens", items: ["User is shown the existing draft brief summary", "Asked: resume from where we left off, or start fresh?", "CONTINUE → Load brief → jump directly to Phase 3 (revision)", "FRESH → Ignore existing brief → Phase 1 (Discovery)"] }, + ], + }, + bs_load_brief: { + title: "Load brief", + color: "#0891b2", + nodeType: "ACTION", + sections: [ + { heading: "What happens", items: ["Agent reads the existing brief file from docs/briefs/", "Provides full context to Phase 3 (revision mode)", "User can iterate on the existing content rather than restarting"] }, + ], + }, + bs_phase1: { + title: "Phase 1 — Discovery", + color: "#2563eb", + nodeType: "MAIN PHASE", + sections: [ + { heading: "Core question", items: ["\"What problem are you trying to solve, and who experiences it?\""] }, + { heading: "Rules", items: ["Max 2 questions at a time — never overwhelm", "Surface the problem, not the solution", "Do not accept vague answers — push for specifics", "Iterate until problem is stated clearly"] }, + { heading: "Exit criteria", items: ["Problem stated in 2–4 sentences", "Primary user named", "Problem is a problem, not a feature"] }, + ], + }, + bs_problem_clear: { + title: "Problem clear?", + color: "#2563eb", + nodeType: "DECISION", + sections: [ + { heading: "Exit criteria", items: ["YES → problem stated in 2–4 clear sentences AND primary user named → Phase 2", "NO → iterate — ask more targeted follow-up questions"] }, + ], + }, + bs_phase2: { + title: "Phase 2 — Deep Dive", + color: "#4f46e5", + nodeType: "MAIN PHASE", + sections: [ + { heading: "Topics to cover", items: ["Scope and boundaries — what is explicitly out of scope?", "Success criteria — how will you know it worked?", "Use cases — top 3–5 concrete scenarios", "Constraints — technical, time, team, budget", "Rejected ideas — what was considered and discarded?"] }, + { heading: "Socratic pressure", items: ["Challenge assumptions — \"Why is X the right approach?\"", "Ask about failure modes — \"What would make this fail?\"", "Probe edges — \"What happens when Y doesn't work?\""] }, + ], + }, + bs_adversarial: { + title: "Adversarial Gate", + color: "#7c3aed", + nodeType: "GATE", + sections: [ + { heading: "Two mandatory questions", items: ["\"What is the strongest case against building this?\"", "\"What would have to be true for this to fail in year 1?\""] }, + { heading: "Purpose", items: ["Forces the user to articulate real risks", "Prevents over-optimistic briefs that skip failure modes", "If user can't answer, the problem statement needs more work"] }, + ], + }, + bs_template_fillable: { + title: "All template sections fillable?", + color: "#7c3aed", + nodeType: "DECISION", + sections: [ + { heading: "Branches", items: ["YES → proceed to Phase 3 (draft + validation)", "NO → iterate back in Phase 2 — identify which sections are still empty"] }, + { heading: "Template sections required", items: ["Problem statement", "Primary user", "Success criteria", "Top use cases", "Constraints", "Out of scope", "Risks / adversarial answers"] }, + ], + }, + bs_phase3: { + title: "Phase 3 — Draft + Validation", + color: "#6d28d9", + nodeType: "MAIN PHASE", + sections: [ + { heading: "What happens", items: ["Agent generates the full brief inline from collected context", "User reviews the draft and provides feedback", "Agent iterates until user confirms the brief is ready", "Quality gate is run before writing to disk"] }, + { heading: "Output format", items: ["Markdown file at docs/briefs/{project-name}.md", "Structured sections: problem, users, success criteria, use cases, constraints, risks"] }, + ], + }, + bs_quality_gate: { + title: "Quality Gate", + color: "#6d28d9", + nodeType: "GATE", + sections: [ + { heading: "Tier 1 — auto-fix silently", items: ["Minor formatting issues", "Incomplete sentences that can be inferred", "Missing punctuation or capitalization"] }, + { heading: "Tier 2 — ask user via question tool", items: ["Ambiguous success criteria", "Conflicting constraints", "Vague scope boundaries"] }, + { heading: "BLOCKED — escalate immediately", items: ["No problem statement at all", "No success criteria", "Empty scope — can't determine what to build"] }, + ], + }, + bs_quality_passed: { + title: "Quality gate passed?", + color: "#6d28d9", + nodeType: "DECISION", + sections: [ + { heading: "Branches", items: ["PASSED → proceed to file write check", "TIER 2 issues → ask user → resolve → re-run gate", "BLOCKED (no problem, no success criteria, empty scope) → STOP — escalate to user, do not write"] }, + ], + }, + bs_file_exists: { + title: "File already exists?", + color: "#7c3aed", + nodeType: "DECISION", + sections: [ + { heading: "Check", items: ["Agent checks if docs/briefs/{project-name}.md already exists on disk"] }, + { heading: "Branches", items: ["NO → write directly", "YES → ask user: overwrite, new version, or rename?"] }, + ], + }, + bs_file_conflict: { + title: "Overwrite / new version / rename?", + color: "#7c3aed", + nodeType: "ACTION", + sections: [ + { heading: "Options", items: ["OVERWRITE → replace existing file with new brief", "NEW VERSION → write as {name}-v2.md (or -v3, etc.)", "RENAME → write with a custom filename provided by the user"] }, + ], + }, + bs_write: { + title: "Write file", + color: "#15803d", + nodeType: "ACTION", + sections: [ + { heading: "What happens", items: ["Agent writes the validated brief to docs/briefs/{project-name}.md", "File is created or overwritten depending on the conflict resolution choice", "Brief is ready for Planning or Orion to consume"] }, + ], + }, + bs_end: { + title: "Brief written", + color: "#1e293b", + nodeType: "DELIVERY", + sections: [ + { heading: "Handoff", items: ["Brief written to docs/briefs/{project-name}.md", "Hand to Planning agent for execution plan", "Or hand to Orion (team-lead) directly for implementation"] }, + ], + }, + bs_esc_blocked: { + title: "Escalation — BLOCKED", + color: "#991b1b", + nodeType: "ESCALATION", + sections: [ + { heading: "When this triggers", items: ["No problem statement at all", "No success criteria defined", "Scope is empty — cannot determine what to build"] }, + { heading: "What happens", items: ["Agent stops immediately — does not write the brief", "Reports precisely what is missing to the user", "User must provide the missing information before continuing"] }, + ], + }, + }, }; } // Y positions map for scroll-to (populated in FlowChart, read in App) const NODE_Y_MAP: Record = {}; +// Y positions map for Brainstorm flowchart scroll-to +const BRAINSTORM_NODE_Y_MAP: Record = {}; + // ─── SVG Flowchart ──────────────────────────────────────────────────────────── const CX = 330; @@ -1073,6 +1550,317 @@ function FlowChart({ selected, onSelect, lang }: { selected: string; onSelect: ( ); } +// ─── Brainstorm Flowchart ───────────────────────────────────────────────────── + +const BS_CX = 330; // main center x +const BS_LX = 100; // left branch x +const BS_RX = 555; // right branch x + +function BrainstormFlowChart({ selected, onSelect, lang }: { selected: string; onSelect: (id: string, nodeY: number) => void; lang: Lang }) { + const { brainstormSvgLabels: L } = getFlowchartData(lang); + const svgWidth = 700; + const svgHeight = 1980; + const ns: NodeProps = { id: "", selected, onSelect }; + + // ── Y positions ── + const Y = { + bs_start: 50, + bs_existing_check: 145, + bs_single_found: 240, // right branch + bs_multi_found: 240, // far right — same row but shifted to RX+30 + bs_status_check: 340, // right branch (continuing from single_found) + bs_ask_continue: 440, // right branch + bs_load_brief: 540, // right + multi load + bs_phase1: 680, + bs_problem_clear: 790, + bs_phase2: 920, + bs_adversarial: 1040, + bs_template_fillable:1140, + bs_phase3: 1280, + bs_quality_gate: 1390, + bs_quality_passed: 1495, + bs_file_exists: 1610, + bs_file_conflict: 1710, + }; + + // The "write" nodes sit at Y_WRITE, end node at Y_END + const Y_WRITE = 1810; + const Y_END = 1910; + + // Populate BRAINSTORM_NODE_Y_MAP + Object.entries(Y).forEach(([k, v]) => { BRAINSTORM_NODE_Y_MAP[k] = v; }); + BRAINSTORM_NODE_Y_MAP["bs_write_overwrite"] = Y_WRITE; + BRAINSTORM_NODE_Y_MAP["bs_write_version"] = Y_WRITE; + BRAINSTORM_NODE_Y_MAP["bs_write_rename"] = Y_WRITE; + BRAINSTORM_NODE_Y_MAP["bs_end"] = Y_END; + BRAINSTORM_NODE_Y_MAP["bs_esc_blocked"] = Y.bs_quality_passed; + + // Widths + const W_P = W_PHASE; + const W_A = W_ACTION; + const W_S = W_SMALL; + + return ( + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + {/* ── SESSION START ── */} + + + + + {/* ── EXISTING BRIEFS? ── */} + + + {/* NO branch from existing_check: goes straight down to Phase 1 */} + + + + + + {/* ── SINGLE FOUND ── */} + + + {/* single_found → status_check */} + + + {/* ── STATUS = DRAFT? ── */} + + + {/* status: YES (draft) → ask_continue (straight down) */} + + + + {/* status: NO → done/other: goes back left to Phase 1 path */} + + + + {/* ── ASK CONTINUE ── */} + + + {/* CONTINUE → load_brief */} + + + + {/* FRESH → Phase 1 (curved back to center) */} + + + + {/* ── LOAD BRIEF ── */} + + + {/* load_brief → phase3 (jump ahead, curved) */} + + + + {/* MULTIPLE branch from existing_check: goes to multi_found (left branch) */} + + + + {/* ── MULTI FOUND ── */} + + + {/* multi: CHOOSE EXISTING → load_brief (curved right + down) */} + + + + {/* multi: NEW PROJECT → Phase 1 */} + + + + {/* ── PHASE 1 — DISCOVERY ── */} + + + + + {/* ── PROBLEM CLEAR? ── */} + + + {/* NO → loop back to Phase 1 */} + + + + {/* YES → Phase 2 */} + + + + {/* ── PHASE 2 — DEEP DIVE ── */} + + + + + {/* ── ADVERSARIAL GATE ── */} + + + + + {/* ── ALL SECTIONS FILLABLE? ── */} + + + {/* NO → back to Phase 2 */} + + + + {/* YES → Phase 3 */} + + + + {/* ── PHASE 3 — DRAFT + VALIDATE ── */} + + + + + {/* ── QUALITY GATE ── */} + + + + + {/* ── QUALITY GATE PASSED? ── */} + + + {/* BLOCKED → escalade (right) */} + + + + + {/* TIER 2 → left branch (ask user → re-run gate) */} + + + + {/* PASSED → file_exists */} + + + + {/* ── FILE ALREADY EXISTS? ── */} + + + {/* NO → write directly */} + + + + {/* YES → file_conflict */} + + + + {/* ── FILE CONFLICT ── */} + + + {/* OVERWRITE → write */} + + + + {/* NEW VERSION → write */} + + + + {/* RENAME → write (right branch) */} + + + + {/* ── WRITE FILE (center — from NEW VERSION) ── */} + + + {/* Left write (OVERWRITE path): arrow from left */} + + + {/* Right write (RENAME path) */} + + + {/* All three write nodes → end */} + + + + + {/* ── END ── */} + + + ); +} + // ─── Detail Panel ───────────────────────────────────────────────────────────── function Code({ children }: { children: string }) { @@ -1146,8 +1934,9 @@ function BulletItem({ item, nodeColor }: { item: string; nodeColor: string }) { } function DetailPanel({ nodeId, lang }: { nodeId: string; lang: Lang }) { - const { details: DETAILS } = getFlowchartData(lang); - const detail = DETAILS[nodeId]; + const { details: DETAILS, brainstormDetails: BS_DETAILS } = getFlowchartData(lang); + const lookupId = nodeId.startsWith("bs_write_") ? "bs_write" : nodeId; + const detail = DETAILS[lookupId] ?? BS_DETAILS[lookupId]; const placeholder = lang === "fr" ? "Cliquer sur un nœud pour voir ses détails." : "Click a node to see its details."; if (!detail) return (
@@ -1281,6 +2070,8 @@ interface Translations { col_mode: string; col_color: string; col_permissions: string; + tab_orion: string; + tab_brainstorm: string; } const translations: Record = { @@ -1524,6 +2315,8 @@ const translations: Record = { col_mode: "Mode", col_color: "Color", col_permissions: "Permissions", + tab_orion: "Orion workflow", + tab_brainstorm: "Brainstorm workflow", }, fr: { plugin_label: "OpenCode Plugin", @@ -1765,6 +2558,8 @@ const translations: Record = { col_mode: "Mode", col_color: "Couleur", col_permissions: "Permissions", + tab_orion: "Workflow Orion", + tab_brainstorm: "Workflow Brainstorm", }, }; @@ -2397,6 +3192,7 @@ export default function App() { const [lang, setLang] = useState("en"); const [selected, setSelected] = useState("understand"); const [zoom, setZoom] = useState(1.0); + const [flowchartTab, setFlowchartTab] = useState<"orion" | "brainstorm">("orion"); const containerRef = useRef(null); const zoomIn = () => setZoom(z => Math.min(2.0, Math.round((z + 0.1) * 10) / 10)); @@ -2412,6 +3208,14 @@ export default function App() { } }; + const handleTabChange = (tab: "orion" | "brainstorm") => { + setFlowchartTab(tab); + setSelected(tab === "orion" ? "understand" : "bs_start"); + setZoom(1.0); + const container = containerRef.current; + if (container) container.scrollTo({ top: 0, behavior: "smooth" }); + }; + const t = translations[lang]; if (view === "intro") { @@ -2474,9 +3278,33 @@ export default function App() { {t.nav_config}
-
- team-lead — Workflow - {t.flowchart_subtitle} + {/* Flowchart tab switcher */} +
+ {([ + { key: "orion" as const, label: t.tab_orion, activeColor: "#4f46e5", activeBg: "white" }, + { key: "brainstorm" as const, label: t.tab_brainstorm, activeColor: "#6d28d9", activeBg: "white" }, + ]).map(tab => ( + + ))}
@@ -2517,7 +3345,10 @@ export default function App() { {/* SVG with zoom */}
- + {flowchartTab === "orion" + ? + : + }
diff --git a/tests/permissions.test.js b/tests/permissions.test.js new file mode 100644 index 0000000..23e2182 --- /dev/null +++ b/tests/permissions.test.js @@ -0,0 +1,41 @@ +// tests/permissions.test.js +// Verifies that all write/edit target directories declared in index.js exist on disk. +// Uses only Node.js built-ins: node:test, node:assert, node:fs/promises, node:path, node:url + +import { describe, test } from "node:test"; +import assert from "node:assert/strict"; +import { readFile, access } from "node:fs/promises"; +import { join } from "node:path"; +import { fileURLToPath } from "node:url"; + +const projectRoot = fileURLToPath(new URL("../", import.meta.url)); + +// ── agent permissions — write/edit target directories ──────────────────────── + +describe("agent permissions — write/edit target directories", () => { + test("all declared write/edit target dirs exist in the repo", async () => { + const indexPath = join(projectRoot, "index.js"); + const content = await readFile(indexPath, "utf-8"); + + // Match paths that appear as "allow" values and end with /** + // Excludes "*" wildcards — we only want specific directory glob targets. + // Pattern: "some/path/**": "allow" or "some/path/**" : "allow" + const matches = content.matchAll(/"([^*"][^"]*\/\*\*)":\s*"allow"/g); + + const dirs = new Set(); + for (const [, path] of matches) { + // Strip the /** suffix to get the base directory + dirs.add(path.replace(/\/\*\*$/, "")); + } + + assert.ok(dirs.size > 0, "expected at least one write/edit target directory in index.js"); + + for (const dir of dirs) { + const absPath = join(projectRoot, dir); + await assert.doesNotReject( + () => access(absPath), + `declared write/edit target directory does not exist: ${dir}` + ); + } + }); +});