@jakkrichm/create-nexus-devflow 2.1.0 → 2.2.1

package/template/.agents/skills/doctor/SKILL.md

@@ -27,8 +27,8 @@ None. `/doctor` takes no argument.
 
 Gather these, then summarize. Do not dump file contents.
 
-1. **Required Blueprint files**
-   - Confirm `AGENTS.md`, `blueprint/`, `devflow/project-plan.md`,
+1. **Required DevFlow files**
+   - Confirm `AGENTS.md`, `devflow/project-plan.md`,
      `devflow/build-plan.md`, and `devflow/context/` exist.
    - Confirm `devflow/context/coding-standards.md`,
      `devflow/context/ai-interaction.md`,
@@ -45,15 +45,22 @@ Gather these, then summarize. Do not dump file contents.
      `### <id> [<severity>] <status> - <title>` and warn on a malformed ledger.
      Report any P0 or P1 finding still `open` or `fixed` by ID, since it will
      block `/complete`. Never block on the ledger yourself.
-   - If `.gitignore` marks Blueprint workflow files as local-only, still require
+   - If `.gitignore` marks DevFlow workflow files as local-only, still require
      the files to exist on disk. Ignored but present is healthy; ignored and
      missing means the local workflow needs to be restored.
 2. **Tool adapters**
-   - Confirm at least one adapter exists: `.agents/skills/` for Codex or
-     `.claude/skills/` for Claude Code.
-   - If both adapters are present, say that is healthy when both tools are used.
-   - If both adapters are present, compare their skill folder names. Warn about
-     missing skills on either side.
+   - Read `.nexus/nexus-devflow.json` when present and report its exact
+     logical adapters: Codex, Claude Code, GitHub Copilot, Antigravity, and OpenCode.
+   - Confirm at least one compatible skill tree exists. Codex, Antigravity, and
+     GitHub Copilot use `.agents/skills/`. Claude Code uses `.claude/skills/`.
+     OpenCode can use either tree.
+   - If both skill trees are present, say that is healthy when the selected
+     tools require both. Compare their skill folder names and warn about missing
+     skills on either side.
+   - If OpenCode is selected, do not require `.opencode/skills/`. If it contains
+     duplicate DevFlow skills alongside `.agents/skills/` or `.claude/skills/`,
+     warn that OpenCode discovers all of those locations and the duplicate tree
+     should be reviewed.
    - If git shows changes under `.agents/skills/` or `.claude/skills/`, check
      the matching adapter file too. Warn when workflow behavior was updated in
      one adapter but not the other.
@@ -62,11 +69,11 @@ Gather these, then summarize. Do not dump file contents.
    - If `CLAUDE.md` exists and still starts with `# Project Name`, flag that
      `/onboard` probably has not finished.
 3. **Commands and project setup**
-   - Check whether root `README.md` is still the copied Blueprint workflow doc
+   - Check whether root `README.md` is still the copied DevFlow workflow doc
      by looking for `# AI Coding Blueprint` or opening text that describes the
-     Blueprint workflow instead of the app. If so, warn that `/onboard` should
+     workflow instead of the app. If so, warn that `/onboard` should
      replace it with a project README before publishing.
-   - If `devflow/README.md` clearly contains copied Blueprint workflow docs,
+   - If `devflow/README.md` clearly contains copied workflow docs,
      report it as an obsolete installer artifact. Its absence is healthy. An
      unchanged managed copy can be removed by the updater; a modified copy needs
      user review.
@@ -84,14 +91,14 @@ Gather these, then summarize. Do not dump file contents.
      detected runtime and package manager, and starts with read-only contents
      permission. Preserve other workflows and report overlap for review.
    - A missing `Verify` command or GitHub workflow is informational. It means the
-     optional automatic-check setup was not selected, not that the Blueprint is
+     optional automatic-check setup was not selected, not that DevFlow is
      unhealthy.
 4. **Ignore rules**
    - Check obvious ignore patterns for the detected stack. For Node or Astro,
      look for `node_modules`, `.env`, `dist`, and framework cache folders such as
      `.astro` or `.next` when relevant.
-   - Detect local-only Blueprint mode if `.gitignore` ignores `.agents/`,
-     `.claude/`, `blueprint/`, or `CLAUDE.md`. Report it as a visibility choice,
+   - Detect local-only DevFlow mode if `.gitignore` ignores `.agents/`,
+     `.claude/`, `devflow/`, or `CLAUDE.md`. Report it as a visibility choice,
      not a failure, when the local files exist.
    - In local-only mode, check whether tracked `AGENTS.md` still describes the
      Blueprint workflow, lists hidden adapter paths, or exposes the core skill
@@ -153,8 +160,8 @@ Choose the repair order in this priority:
 - Required Blueprint files missing -> overlay the Blueprint again, or use
   `/adopt` for a brownfield app.
 - No git repo -> initialize git before using the build loop.
-- No tool adapter -> restore `.agents/skills/` or `.claude/skills/` for the tool
-  being used.
+- No tool adapter -> restore `.agents/skills/` or `.claude/skills/` for the
+  selected tool. OpenCode can use either compatible tree.
 - Onboarding incomplete -> run `/onboard`.
 - Root README is still the Blueprint workflow doc -> run `/onboard` to replace
   it with a project README before publishing.

package/template/.agents/skills/feature/SKILL.md

@@ -32,6 +32,7 @@ big item has been split into sub-items, the next unchecked sub-item is the targe
 
 ## Step 1 - pick the target
 
+- Given a Discovery ID or Idea ID (e.g. `/feature DISC-20260824-001` or `/feature IDEA-001`) -> import problem context, research, trade-offs, and ADRs from `devflow/discoveries/{DISC-ID}/discovery.md` or `devflow/ideas.md` into the living spec.
 - Given a number or name that matches a build-plan item -> use it.
 - Given a request that clearly describes a new feature with no reasonable match
   in the build plan -> follow **New-feature intake** below.

package/template/.agents/skills/grill/SKILL.md

@@ -0,0 +1,93 @@
+---
+name: grill
+description: "[devflow][B] Interactive Socratic alignment & domain modeling - stress-test plans, extract domain glossary, and record architecture decision records (ADRs) before delivery."
+argument-hint: "{topic, plan, or question}"
+---
+
+# grill - Socratic Alignment & Domain Modeling
+
+$ARGUMENTS
+
+Use this skill to conduct a codebase-grounded, interactive Socratic interview with the user. It clarifies domain vocabulary, resolves architectural ambiguities, and prevents misalignment before writing specifications or code.
+
+## Invocations & Aliases
+
+- `/grill {topic or plan}`: Standard slash command in Claude Code, Google Antigravity, and Gemini CLI
+- `grill {topic or plan}`: Plain text invocation
+- `$grill {topic or plan}`: Codex CLI invocation
+- `/align {topic}`: Alias for domain alignment
+
+## Core Philosophy: Align Before You Build
+
+1. **Codebase-Grounded**: Read existing code and context first. Never ask questions the codebase can already answer.
+2. **One Round at a Time**: Ask 1-2 focused, high-leverage questions per round with clear recommended defaults. Never dump a wall of 10 questions.
+3. **Lazy Inline Persistence**:
+   - Write agreed domain terminology to `devflow/context/glossary.md` the moment each term resolves.
+   - Record significant, hard-to-reverse technical decisions as ADRs in `devflow/decisions/ADR-xxx-{slug}.md`.
+4. **Zero Assumptions**: Challenge ambiguities, contradictory requirements, and naming inconsistencies upfront.
+
+---
+
+## Process & Execution Loop
+
+### 1. Grounding Phase (Silent Inspection)
+Before asking the first question:
+- Read `devflow/context/project-overview.md` and `devflow/context/coding-standards.md`.
+- Inspect existing domain terms in `devflow/context/glossary.md` (if present).
+- Search codebase patterns (`grep_search` / `rg`) related to the topic to ground technical reality.
+
+### 2. Interactive Socratic Interview Loop
+In each turn:
+- Identify the most critical unresolved branch in the design tree:
+  - **Domain Language & Boundaries**: "What exactly is an Entity X versus Entity Y in this context?"
+  - **Data Flow & Contracts**: "Who owns state X? Synchronous vs. asynchronous?"
+  - **Edge Cases & Failure Modes**: "What happens on network failure, concurrent mutation, or invalid input?"
+  - **Irreversible Trade-offs**: "Database schema change vs. application-layer adapter?"
+- Ask **1-2 questions maximum** per turn.
+- Always provide a recommended default with concise technical rationale.
+- Wait for the user's answer.
+
+### 3. Immediate State Persistence
+
+#### A. Domain Glossary (`devflow/context/glossary.md`)
+When a domain term or conceptual definition crystallizes, immediately create or append to `devflow/context/glossary.md`:
+
+```markdown
+### [Term / Concept]
+- **Definition**: Clear, unambiguous definition within this project.
+- **Constraints**: Invariants, boundaries, or lifecycle rules.
+- **Aliases / Related**: Related terms or common misnomers.
+```
+
+#### B. Architecture Decision Records (`devflow/decisions/ADR-xxx-{slug}.md`)
+When a decision meets the 3 ADR criteria:
+1. **Significant Impact**: Affects architecture, data schema, security, or public API.
+2. **Hard to Reverse**: Changing it later requires painful migration or refactoring.
+3. **Multiple Viable Alternatives**: There were real trade-offs between 2+ options.
+
+Allocate the next sequential ID (`ADR-001`, `ADR-002`, ...) and create `devflow/decisions/ADR-xxx-{slug}.md`:
+
+```markdown
+# ADR-xxx: {Title}
+
+- **Status**: Accepted
+- **Date**: {YYYY-MM-DD}
+- **Context**: {Why was this decision needed? What problem does it solve?}
+- **Decision**: {What did we decide to do?}
+- **Alternatives Considered**:
+  - *Option 1*: {Pros / Cons}
+  - *Option 2*: {Pros / Cons}
+- **Consequences**:
+  - *Positive*: {Benefits gained}
+  - *Trade-offs / Risks*: {Costs, constraints, or follow-ups}
+```
+
+---
+
+## 4. Closing & Handoff
+
+When all design branches are resolved:
+1. Summarize settled domain terms and created ADRs.
+2. Provide explicit next command recommendations:
+   - **Fast-Track (Standard Features/Fixes)**: Run `/feature {topic}` or `/fix {topic}` to immediately start the living spec.
+   - **Deep-Track (Large Architectural Epics)**: Run `10-define` or `/discovery` with the discovery context.

package/template/.agents/skills/implement/SKILL.md

@@ -65,7 +65,7 @@ Before the first rollback build step:
    and the only dirty path before applying the patch is the approved rollback
    spec. Stop on drift.
 3. Preview the target's product diff while excluding `.agents/**`, `.claude/**`,
-   `blueprint/**`, `AGENTS.md`, `CLAUDE.md`, and
+   `devflow/**`, `AGENTS.md`, `CLAUDE.md`, and
    `prototypes/**`. Confirm the preview is non-empty and matches the Product
    paths in the spec.
 4. Apply that product diff in reverse with three-way conflict detection and
@@ -73,7 +73,7 @@ Before the first rollback build step:
 
        git diff --binary <target-parent> <target-commit> -- . \
          ':(exclude).agents/**' \
-         ':(exclude).claude/**' ':(exclude)blueprint/**' \
+         ':(exclude).claude/**' ':(exclude)devflow/**' \
          ':(exclude)AGENTS.md' ':(exclude)CLAUDE.md' \
          ':(exclude)prototypes/**' |
          git apply --reverse --3way --index

package/template/.agents/skills/onboard/SKILL.md

@@ -69,7 +69,7 @@ obsolete overlay content in the product README slot:
 - Create a small root `README.md` stub for the actual project using the detected
   project name, one-line purpose when known, and the Commands from `AGENTS.md`.
   Keep it minimal if the project plan is not filled yet.
-- Do not move or copy the workflow document into `blueprint/`. Agents use the
+- Do not move or copy the workflow document into `devflow/`. Agents use the
   local skills, plans, and context files directly.
 - Remove any `AGENTS.md` claim that a project README explains the Blueprint
   workflow.
@@ -91,7 +91,7 @@ If no test command exists, say so explicitly. Do not claim tests are a gate unti
 a real test command is configured.
 
 If `CLAUDE.md` exists and still has the placeholder `# Project Name`, replace it
-with the detected project name. Keep the `@AGENTS.md` and `@blueprint/...`
+with the detected project name. Keep the `@AGENTS.md` and `@devflow/...`
 imports intact. Do not move detailed app context into `CLAUDE.md`; that belongs
 in `AGENTS.md` and the generated project overview.
 
@@ -147,17 +147,17 @@ preserving existing entries. Typical examples include dependencies, build output
 framework caches, logs, environment files, test output, temporary files, and OS or
 editor files.
 
-Ask how Blueprint workflow files should be handled in git, unless the user
+Ask how DevFlow workflow files should be handled in git, unless the user
 already gave a preference:
 
 ```text
-Blueprint visibility?
+DevFlow visibility?
 
-1. Commit Blueprint workflow files
+1. Commit DevFlow workflow files
    Portable. Best for teams and working across machines.
 
-2. Keep Blueprint workflow files local
-   Adds .agents/, .claude/, blueprint/, and CLAUDE.md to .gitignore.
+2. Keep DevFlow workflow files local
+   Adds .agents/, .claude/, devflow/, and CLAUDE.md to .gitignore.
    Keeps AGENTS.md public as the lightweight project agent guide.
 ```
 
@@ -166,37 +166,38 @@ Recommend option 1 by default. If the user chooses option 2:
 - Add this block to `.gitignore`, preserving existing entries:
 
   ```gitignore
-  # AI Blueprint local workflow files
+  # DevFlow local workflow files
   .agents/
   .claude/
-  blueprint/
+  devflow/
   CLAUDE.md
   ```
 
 - Keep `AGENTS.md` tracked. It remains the lightweight public project guide for
   commands and conventions.
 - Make `AGENTS.md` public-safe: keep project description, commands, testing gate,
-  and coding conventions, but remove or avoid Blueprint workflow explanations,
+  and coding conventions, but remove or avoid DevFlow workflow explanations,
   hidden adapter paths, workflow-document pointers, and core skill lists that
   would expose the local-only workflow.
 - Explain that local-only mode hides the workflow contents from the repo, but the
   `.gitignore` names still reveal the ignored paths.
-- Explain that Blueprint state, specs, findings, and history will not travel
-  with the repo; another machine needs the Blueprint reinstalled or restored
+- Explain that DevFlow state, specs, findings, and history will not travel
+  with the repo; another machine needs DevFlow reinstalled or restored
   locally.
-- If any of `.agents/`, `.claude/`, `blueprint/`, or
+- If any of `.agents/`, `.claude/`, `devflow/`, or
   `CLAUDE.md` are already tracked, say `.gitignore` will not hide tracked files.
   Ask before running
-  `git rm --cached -r .agents .claude blueprint CLAUDE.md`, and
+  `git rm --cached -r .agents .claude devflow CLAUDE.md`, and
   only run it if the user explicitly approves. Never delete the local files.
 
 Then report which adapter folders are needed:
 
-- Codex only: keep `AGENTS.md`, `.agents/`, and `blueprint/`; `CLAUDE.md` and
+- Codex, Antigravity, and GitHub Copilot: keep `AGENTS.md`, `.agents/`, and `devflow/`; `CLAUDE.md` and
   `.claude/` can be deleted.
-- Claude Code only: keep `AGENTS.md`, `CLAUDE.md`, `.claude/`, and `blueprint/`;
+- Claude Code only: keep `AGENTS.md`, `CLAUDE.md`, `.claude/`, and `devflow/`;
   `.agents/` can be deleted.
-- Mixed tools: keep both adapters.
+- OpenCode: shares either `.agents/` or `.claude/` compatible skill tree without duplicate folders.
+- Mixed tools: keep both `.agents/` and `.claude/` adapters.
 
 Do not delete adapters unless the user explicitly asks.
 

package/template/.agents/skills/rollback/SKILL.md

@@ -71,7 +71,7 @@ changed. Exclude these protected workflow paths:
 
 - `.agents/**`
 - `.claude/**`
-- `blueprint/**`
+- `devflow/**`
 - `AGENTS.md`
 - `CLAUDE.md`
 - `prototypes/**`

package/template/.claude/skills/10-define/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: 10-define
-description: "[Devflow] Define stage in DevFlow 2.0 - turn an approved discovery into a bounded delivery run in context/current-run with stable scope."
+description: "[devflow][D] Define stage in DevFlow 2.0 - turn an approved discovery into a bounded delivery run in context/current-run with stable scope."
 argument-hint: "{approved discovery-id, discovery path, running-id, or run path}"
 ---
 
@@ -43,7 +43,7 @@ using:
 Require:
 - `Decision: Proceed`
 - `Approval Status: Approved`
-- A resolvable Discovery ID and `00-explore.md`
+- A resolvable Discovery ID and `discovery.md` (or legacy `00-explore.md`)
 
 ### 3. Allocate Sequential ID
 - Inspect `devflow/history/HISTORY.md` and allocate sequential ID without prefix (e.g. `022-{slug}`).
@@ -51,4 +51,4 @@ Require:
 - Write `devflow/context/current-run/10-define.md`.
 - Update `devflow/context/current-stage.md`:
   - `Active Running ID`: `{ID}`
-  - `Current Stage`: `10-define (Completed -> Ready for 20-spec)`
+  - `Current Stage`: `10-define (Completed -> Ready for 20-spec)`

package/template/.claude/skills/20-spec/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: 20-spec
-description: "[Devflow] Spec stage in DevFlow 2.0 - write the formal markdown-first specification from a stable definition."
+description: "[devflow][D] Spec stage in DevFlow 2.0 - write the formal markdown-first specification from a stable definition."
 argument-hint: "{running-id or workspace path}"
 ---
 
@@ -153,4 +153,3 @@ Report:
 - Use `Research` when a requirement, rule, or integration constraint still lacks evidence.
 - Use `Spec-Research`, `Competitor`, or `PRD` when the contract needs stronger external, product, or market framing before planning.
 - Use `grill-with-docs` when available if clarification could materially change acceptance criteria, edge cases, exclusions, or rules.
-

package/template/.claude/skills/30-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: 30-plan
-description: "[Devflow] Plan stage in DevFlow 2.0 - transform 20-spec.md into an executable task breakdown with test decisions."
+description: "[devflow][D] Plan stage in DevFlow 2.0 - transform 20-spec.md into an executable task breakdown with test decisions."
 ---
 # Phase 30: Plan Implementation
 
@@ -218,4 +218,3 @@ If `Approval Status` is still pending or major dependencies remain unresolved:
 - **Reason**: Plans often discover stable patterns that future sessions should reuse.
 - **Suggested Command**: `Wiki project ingest devflow/runs/{ID}-*30-plan.md`
 
-

package/template/.claude/skills/40-execute/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: 40-execute
-description: "[Devflow] Execute stage in DevFlow 2.0 - execute planned tasks incrementally with evidence and unit tests."
+description: "[devflow][D] Execute stage in DevFlow 2.0 - execute planned tasks incrementally with evidence and unit tests."
 ---
 # Phase 40: Execute Code
 
@@ -158,4 +158,4 @@ Report:
 - **Needed**: `yes` when coding discovers a reusable implementation pattern, gotcha, or context optimization.
 - **Scope**: `project` unless the discovery is about DevFlow itself.
 - **Reason**: Coding findings are useful only when they are stable enough to help future tasks.
-- **Suggested Command**: `Wiki project ingest devflow/runs/{ID}-*40-execute.md`
+- **Suggested Command**: `Wiki project ingest devflow/runs/{ID}-*40-execute.md`

package/template/.claude/skills/50-verify/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: 50-verify
-description: "[Devflow] Verify stage in DevFlow 2.0 - perform senior QA review, record evidence, and decide pass or return-to-implement."
+description: "[devflow][D] Verify stage in DevFlow 2.0 - perform senior QA review, record evidence, and decide pass or return-to-implement."
 ---
 
 # Phase 50: Verify Quality
@@ -52,4 +52,4 @@ Execute verification across all essential quality dimensions:
 Report:
 - QA verdict across all verification lanes
 - Evidence commands and outputs
-- Next command: `60-report {ID}` (if pass) or `40-execute {ID}` (if fail)
+- Next command: `60-report {ID}` (if pass) or `40-execute {ID}` (if fail)

package/template/.claude/skills/60-report/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: 60-report
-description: "[Devflow] Report stage in DevFlow 2.0 - produce standardized markdown summary report with retrospective lessons learned."
+description: "[devflow][D] Report stage in DevFlow 2.0 - produce standardized markdown summary report with retrospective lessons learned."
 argument-hint: "{running-id or workspace path}"
 ---
 
@@ -54,4 +54,4 @@ Structure the report in **Thai (`th`)**:
 ## Next Workflow Recommendation
 
 - **Primary**: `70-deliver {ID}`
-- **Optional Standalone HTML**: `/report:html`
+- **Optional Standalone HTML**: `/report:html`

package/template/.claude/skills/70-deliver/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: 70-deliver
-description: "[Devflow] Deliver stage in DevFlow 2.0 - package verified work for delivery, archive run to categorized history, git merge, PR, or deployment."
+description: "[devflow][D] Deliver stage in DevFlow 2.0 - package verified work for delivery, archive run to categorized history, git merge, PR, or deployment."
 argument-hint: "{running-id or workspace path}"
 ---
 
@@ -69,4 +69,4 @@ Set `devflow/context/current-stage.md` to:
 - `Active Running ID`: `None (Idle)`
 - `Current Stage`: `Idle (Ready for new run)`
 - `Last Completed Run`: `{ID} ({YYYY-MM-DD})`
-- `Last Updated`: `{YYYY-MM-DD}`
+- `Last Updated`: `{YYYY-MM-DD}`