@jakkrichm/create-nexus-devflow 2.0.6 → 2.0.9

package/template/.claude/skills/server-management/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: server-management
-description: Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
+description: "[Devflow] Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands."
 allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
 

package/template/.claude/skills/shipping-and-launch/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: shipping-and-launch
-description: Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
+description: "[Devflow] Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy."
 ---
 
 # Shipping and Launch

package/template/.claude/skills/silent-failure-audit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: silent-failure-audit
-description: Audits error handling, logging, fallbacks, and observability for silent failures. Use after adding catch blocks, fallback logic, retry handling, optional chaining, or user-facing failure paths.
+description: "[Devflow] Audits error handling, logging, fallbacks, and observability for silent failures. Use after adding catch blocks, fallback logic, retry handling, optional chaining, or user-facing failure paths."
 ---
 
 # Silent Failure Audit

package/template/.claude/skills/simplify/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: simplify
-description: Simplify workflow
+description: "[Devflow] Code simplification and refactoring for clarity and maintainability without altering runtime behavior."
 ---
 
 ---

package/template/.claude/skills/skill-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: skill-development
-description: Guides the creation and maintenance of agent skills. Use when building new skills or modifying existing ones to ensure they follow the PRP framework standards.
+description: "[Devflow] Guides the creation and maintenance of agent skills. Use when building new skills or modifying existing ones to ensure they follow the PRP framework standards."
 ---
 
 # Skill Development (Skill Anatomy)

package/template/.claude/skills/spec-driven-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: spec-driven-development
-description: Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
+description: "[Devflow] Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea."
 ---
 
 # Spec-Driven Development

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

@@ -1,6 +1,6 @@
 ---
 name: spec-orchestration
-description: Coordinate Brainstorm, Research, PRD, competitor context, and spec critique before the work re-enters the numbered mainline. Use when a broad idea needs orchestration rather than a straight pass.
+description: "[Devflow] Coordinate Brainstorm, Research, PRD, competitor context, and spec critique before the work re-enters the numbered mainline. Use when a broad idea needs orchestration rather than a straight pass."
 ---
 
 # Spec Orchestration

package/template/.claude/skills/specialist-agent-routing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: specialist-agent-routing
-description: Route a request to the right specialist agent and preserve the DevFlow 2.0 stage-first contract. Use when the user wants direct specialist judgment on a file, folder, workspace, or concern.
+description: "[Devflow] Route a request to the right specialist agent and preserve the DevFlow 2.0 stage-first contract. Use when the user wants direct specialist judgment on a file, folder, workspace, or concern."
 ---
 
 # Specialist Agent Routing

package/template/.claude/skills/tailwind-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: tailwind-patterns
-description: Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.
+description: "[Devflow] Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture."
 allowed-tools: Read, Write, Edit, Glob, Grep
 ---
 

package/template/.claude/skills/test/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: test
-description: Test workflow
+description: "[Devflow] Test execution, missing test generation, and coverage analysis across unit, integration, and smoke test suites."
 ---
 
 ---

package/template/.claude/skills/test-driven-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: test-driven-development
-description: Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
+description: "[Devflow] Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality."
 ---
 
 # Test-Driven Development

package/template/.claude/skills/test-execution-and-coverage/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: test-execution-and-coverage
-description: Generate missing tests, run existing tests, and summarize coverage and failures. Use when implementation or verification needs explicit testing evidence beyond a general TDD reminder.
+description: "[Devflow] Generate missing tests, run existing tests, and summarize coverage and failures. Use when implementation or verification needs explicit testing evidence beyond a general TDD reminder."
 ---
 
 # Test Execution And Coverage

package/template/.claude/skills/try/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: try
+description: "[Devflow] Generate human manual QA review walkthrough guide (where to go, what to click, what to expect)."
+---
+
+# try - Manual QA & Review Walkthrough Guide
+
+Where this sits in the workflow:
+
+```text
+/40-implement or /50-verify or /60-report  ->  [try]  ->  human review & verification
+(work implemented / verified)                  (manual    (where to go,
+                                               steps)     what to click)
+```
+
+`/50-verify` proves behavior from automated QA and test runs. `/try` gives the user and testers an actionable, step-by-step manual walkthrough: start this command, open this route, click these controls, expect this result, and watch for these failure signs.
+
+It is always **read-only 100%**. It does not edit files, install dependencies, commit, merge, push, or run destructive commands.
+
+## Input
+
+Optional scope:
+
+- **no argument**: use the active run in `devflow/context/current-stage.md` (or the latest completed run under `devflow/runs/`)
+- `latest`: use the most recent completed run in `devflow/runs/`
+- a run ID or path: e.g. `/try RUN-002-add-onboard-adopt-doctor-skills`
+- a specific route, endpoint, or CLI command: focus the walkthrough on that surface
+
+If there is no active run and no run history, ask what change or feature the user wants to test manually.
+
+## Step 1 - Find The Work To Explain
+
+Read:
+
+- `AGENTS.md` (Commands section)
+- `devflow/context/current-stage.md`
+- `devflow/context/project-overview.md`
+- `devflow/context/coding-standards.md`
+- Active run artifacts: `20-spec.md`, `30-plan.md`, `40-implement.md`, `50-verify.md` (or archived run artifacts)
+- Current git branch and status
+
+Do not dump the full spec. Extract only the concrete routes, screens, CLI commands, API endpoints, test data, and expected outcomes that a human needs to verify the feature.
+
+## Step 2 - Identify How To Run The App
+
+Check the Commands section in `AGENTS.md`. Adapt to the project type:
+
+- **Web app**: dev server command (e.g. `npm run dev`), local URL (e.g. `http://localhost:3000`), and specific route/screen.
+- **Server / API**: start command, base URL, endpoint, HTTP method, payload, and expected response shape.
+- **CLI**: exact CLI command, flags, arguments, and expected terminal output.
+- **Library / Module**: sample usage snippet, REPL call, or interactive test command.
+- **Fullstack / Microservices**: minimal combined startup commands (e.g. backend + frontend).
+
+If a startup command is missing or unclear in `AGENTS.md`, report that as a configuration gap rather than guessing.
+
+## Step 3 - Produce The Manual Walkthrough Guide
+
+Format the guide with these 5 standard sections:
+
+1. **1. Start** - exact command(s) to start the system and where to run them.
+2. **2. Open** - URL(s), screens, tabs, API endpoints, or terminal locations.
+3. **3. Do** - specific clicks, form inputs, toggles, selections, or arguments.
+4. **4. Expect** - expected visible UI change, response payload, state change, output, or absence of errors.
+5. **5. Watch For** - common failure symptoms, console errors, network 4xx/5xx errors, stale state, layout breakage, or safety warnings.
+
+### Example Walkthrough Style:
+
+```markdown
+### 1. Start
+Run `npm run dev` in the project root.
+
+### 2. Open
+Navigate to `http://localhost:3000/dashboard/reports`.
+
+### 3. Do
+1. Click the **"Export Report"** button in the top right.
+2. Select **"Format: HTML"** from the dropdown.
+3. Click **"Download"**.
+
+### 4. Expect
+- A new file `report.html` is downloaded.
+- The UI displays a green success toast: *"Report exported successfully"*.
+- The downloaded HTML file opens in the browser with full styling and charts.
+
+### 5. Watch For
+- Spinner hanging indefinitely without downloading.
+- Console error related to `Blob` or `URL.createObjectURL`.
+- Broken styling or unrendered Mermaid charts in the exported HTML.
+```
+
+## Step 4 - Include Confidence, Best Signal & Gaps
+
+Conclude with:
+
+- **Best Signal**: the single most critical action the user should try first to confirm functionality.
+- **Edge Cases & Error Flows**: optional secondary checks (e.g. invalid input, empty state, network failure).
+- **Gaps & Assumptions**: anything the guide cannot know for certain (e.g. seed credentials, third-party API keys, required database fixtures).
+
+## Rules
+
+- **Strictly Read-Only**: Never edit code, commit, push, install packages, or mutate repository state.
+- **Do Not Run Automatically**: Do not launch the server or run commands unless the user explicitly instructs you to do so in the chat.
+- **Be Concrete & Specific**: Provide exact URLs, button labels, and payloads.
+- **Acknowledge Uncertainty**: If a route or behavior is not specified in the spec, state it clearly as an assumption.
+
+## Output Formatting
+
+Follow the project conventions in `devflow/context/ai-interaction.md`: concise, scannable markdown with numbered steps and clear bold headers.

package/template/.claude/skills/type-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: type-design
-description: Analyzes type and interface design for encapsulation, invariant expression, usefulness, and enforcement. Use when introducing new types, reviewing PRs with type changes, or refactoring domain models.
+description: "[Devflow] Analyzes type and interface design for encapsulation, invariant expression, usefulness, and enforcement. Use when introducing new types, reviewing PRs with type changes, or refactoring domain models."
 ---
 
 # Type Design

package/template/.claude/skills/ui-ux-pro-max/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ui-ux-pro-max
-description: AI-powered design intelligence with 50+ styles, 95+ color palettes, and automated design system generation. Use when designing, building, or reviewing UI/UX.
+description: "[Devflow] AI-powered design intelligence with 50+ styles, 95+ color palettes, and automated design system generation. Use when designing, building, or reviewing UI/UX."
 ---
 
 # UI/UX Pro Max (Design Intelligence)

package/template/.claude/skills/using-agent-skills/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: using-agent-skills
-description: Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
+description: "[Devflow] Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked."
 ---
 
 # Using Agent Skills

package/template/.claude/skills/verification-orchestration/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: verification-orchestration
-description: Coordinate multi-lane QA, specialist review, test planning, and verification follow-up. Use when /50-Verify needs more structure than a single pass and the team needs a QA matrix or specialist routing.
+description: "[Devflow] Coordinate multi-lane QA, specialist review, test planning, and verification follow-up. Use when /50-Verify needs more structure than a single pass and the team needs a QA matrix or specialist routing."
 ---
 
 # Verification Orchestration

package/template/.claude/skills/vulnerability-scanner/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vulnerability-scanner
-description: Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
+description: "[Devflow] Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization."
 allowed-tools: Read, Glob, Grep, Bash
 ---
 

package/template/.claude/skills/wiki/SKILL.md

@@ -1,6 +1,6 @@
 ---name: wiki
 
-description: DevFlow Wiki - Ingest, query, lint, and promote compiled project or framework knowledge.
+description: "[Devflow] Knowledge base management, ingestion, linting, and querying under devflow/wiki/."
 ---
 # Wiki
 

package/template/.claude/skills/workflow-documentation-sync/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-documentation-sync
-description: Enforces the synchronization and comprehensive update of documentation, manuals, usage guides, and examples whenever a new workflow is introduced or modified in the project. Use when introducing new workflows or changing existing ones.
+description: "[Devflow] Enforces the synchronization and comprehensive update of documentation, manuals, usage guides, and examples whenever a new workflow is introduced or modified in the project. Use when introducing new workflows or changing existing ones."
 ---
 
 # Workflow Documentation Sync

package/template/AGENTS.md

@@ -6,42 +6,122 @@ Instructions for AI coding agents working in this project. This is the cross-too
 
 This project uses **Nexus-DevFlow**, an agentic stage-based workflow layer. To start a new project, scaffold the application first in an empty folder, then run `npx @jakkrichm/create-nexus-devflow` to overlay DevFlow onto your codebase.
 
-## Tool-Specific Adapters
+## Read these for full context
+
+- `devflow/context/project-overview.md` - the project's source of truth
+- `devflow/context/coding-standards.md` - engineering conventions & rules to follow
+- `devflow/context/ai-interaction.md` - how to interact with the user on this project
+- `devflow/context/current-stage.md` - active discovery or running delivery state
+- `devflow/context/findings.md` - quality, security, and verification ledger
+
+## Tool-Specific Adapters & Execution Rules
 
 The workflow and skills are exposed through tool-specific adapters:
 
-- **Codex & Google Antigravity**: `.agents/skills/<skill>/SKILL.md`
+- **OpenAI Codex & Google Antigravity**: `.agents/skills/<skill>/SKILL.md`
 - **Claude Code**: `.claude/skills/<skill>/SKILL.md`
 
 Unused adapter families can be removed. Codex and Antigravity projects keep `.agents/` and `AGENTS.md`. Claude Code projects keep `.claude/` and `AGENTS.md` (via `CLAUDE.md`).
 
+### Universal Invocation & Agent Directives:
+
+1. **Universal Command Names**: You can invoke workflows using plain stage names (`00-discover`, `10-define`, `20-spec`, `30-plan`, `40-implement`, `50-verify`, `60-report`, `70-release`, `devflow`), semantic aliases (`discover`, `define`, `spec`, `plan`, `implement`, `verify`, `report`, `release`, `status`), slash commands (`/00-discover`, `/devflow`), Codex skill format (`$00-discover`, `$spec`), or natural language intents (e.g., "start discovery", "write spec", "implement next step").
+2. **OpenAI Codex & Non-Native CLI Tools**: In environments without automatic background skill discovery (such as OpenAI Codex CLI, Aider, or generic terminals), **you MUST use your file reading tool to inspect `.agents/skills/<skill>/SKILL.md` before executing the stage** to strictly follow its schema, artifact contract, and quality gates.
+3. **Google Antigravity & Claude Code**: Native skill engines automatically discover and surface `.agents/skills/` and `.claude/skills/`.
+4. **State-Aware Inspection**: When unsure what to do next, invoke `devflow` (or `/devflow`, `$devflow`) to automatically inspect `devflow/context/current-stage.md` and active runs in `devflow/runs/`.
+5. **Default Artifact & Communication Language (Thai)**: All generated markdown stage artifacts (`00-discover.md`, `10-define.md`, `20-spec.md`, `30-plan.md`, `40-implement.md`, `50-verify.md`, `60-report.md`, `70-release.md`) and user communication MUST default to **Thai (`th`)**, while code, technical terms, file paths, and identifiers remain in English.
+
 ## Timeline Workflow
 
 ```text
-/00-Discover -> /10-Define -> /20-Spec -> /30-Plan -> /40-Implement -> /50-Verify -> /60-Report -> /70-Release
+00-discover -> 10-define -> 20-spec -> 30-plan -> 40-implement -> 50-verify -> 60-report -> 70-release
 ```
 
 ### Mainline Stages:
-1. `/00-Discover` - Explore a request before delivery commitment. Creates a Discovery ID (`devflow/discoveries/...`).
-2. `/10-Define` - Turn an approved discovery into one or more bounded delivery runs (`devflow/runs/{running-id}/10-define.md`).
-3. `/20-Spec` - Formalize markdown-first specifications (`20-spec.md`).
-4. `/30-Plan` - Transform spec into executable steps (`30-plan.md`).
-5. `/40-Implement` - Execute planned tasks incrementally (`40-implement.md`).
-6. `/50-Verify` - Run Senior QA review and validation check (`50-verify.md`).
-7. `/60-Report` - Produce markdown and HTML summary report (`60-report.md`, `60-report.html`).
-8. `/70-Release` - Package verified work for merge, PR, or deployment (`70-release.md`).
+
+1. `00-discover` (alias: `discover`, `/00-discover`, `$00-discover`)
+   - **Purpose**: Explore a request before delivery commitment without allocating a running ID.
+   - **Artifact**: `devflow/discoveries/{discovery-id}-{slug}/00-discover.md`
+   - **Gate**: Produces `Proceed`, `Defer`, or `Reject` decision.
+
+2. `10-define` (alias: `define`, `/10-define`, `$10-define`)
+   - **Purpose**: Turn an approved discovery into one or more bounded delivery runs with stable scope and sequential Running IDs.
+   - **Artifact**: `devflow/runs/{running-id}-{slug}/10-define.md`
+   - **Gate**: Approved run map and explicit in-scope / out-of-scope boundaries.
+
+3. `20-spec` (alias: `spec`, `/20-spec`, `$20-spec`)
+   - **Purpose**: Formalize markdown-first delivery contract and testable acceptance criteria from a stable definition.
+   - **Artifact**: `devflow/runs/{running-id}-{slug}/20-spec.md`
+   - **Gate**: Unambiguous acceptance criteria and hard constraints.
+
+4. `30-plan` (alias: `plan`, `/30-plan`, `$30-plan`)
+   - **Purpose**: Transform `20-spec.md` into phased executable tasks with explicit test decisions (Required / Manual / Not Required).
+   - **Artifacts**: `30-plan.md`, `checklists/implementation-checklist.md`, `checklists/verification-checklist.md`
+   - **Gate**: Ordered dependencies, scoped subtasks, and TDD decisions.
+
+5. `40-implement` (alias: `implement`, `/40-implement`, `$40-implement`)
+   - **Purpose**: Execute planned tasks incrementally one scoped unit at a time behind review gates.
+   - **Artifact**: `40-implement.md` (and updated checklists)
+   - **Gate**: Code changes tested, verification recorded, deviations documented.
+
+6. `50-verify` (alias: `verify`, `/50-verify`, `$50-verify`)
+   - **Purpose**: Senior QA review and multi-lane validation check across functionality, regressions, and quality standards.
+   - **Artifact**: `50-verify.md` (optional `50-verify-impact.md`)
+   - **Gate**: Pass or return-to-implement decision with evidence.
+
+7. `60-report` (alias: `report`, `/60-report`, `$60-report`)
+   - **Purpose**: Produce the standardized final markdown and self-contained HTML summary report for the completed run.
+   - **Artifacts**: `60-report.md`, `60-report.html`
+   - **Gate**: Completed delivery digest ready for stakeholder review.
+
+8. `70-release` (alias: `release`, `/70-release`, `$70-release`)
+   - **Purpose**: Package verified work for delivery, git merge, pull request, changelog update, or deployment.
+   - **Artifact**: `70-release.md`
+   - **Gate**: Safe handoff, release notes, and deployment readiness.
 
 ### Public Companion Commands:
-- `Goal`: Route broad goals before Discovery
-- `Brainstorm`: Brainstorm ideas without creating running IDs
-- `Research`: Conduct codebase or web research
-- `Debug`: Root cause investigation before/during implementation
-- `PRD`: Product framing before delivery commitment
-- `Issue-Triage`: Intaking and triaging incoming reports
-- `Security-Review`: High-severity security review
-- `Wiki`: Knowledge base management under `devflow/wiki/`
-- `Check-For-Updates`: Verify or upgrade DevFlow setup
-- `Help`: Routing and process assistance
+
+- `devflow` (alias: `status`, `/devflow`, `$devflow`): Flagship interactive guide, state inspector, and intent router.
+- `onboard` (alias: `/onboard`, `$onboard`): Initial stack detection and baseline setup for fresh/scaffolded projects.
+- `adopt` (alias: `/adopt`, `$adopt`): Survey existing brownfield codebases and bootstrap DevFlow context.
+- `doctor` (alias: `/doctor`, `$doctor`): Read-only health check for context files, adapters, commands, and workflow drift.
+- `try` (alias: `/try`, `$try`): Step-by-step human manual QA review guide (where to go, what to click, what to expect).
+- `rollback` (alias: `/rollback`, `$rollback`): Safe feature/run reversal planner with dependency and commit risk analysis.
+- `ci` (alias: `/ci`, `$ci`): Automatic GitHub Actions workflow (`.github/workflows/verify.yml`) setup and alignment.
+- `brief` (alias: `/brief`, `$brief`): Read-only scope, dependency, and size pre-briefing before speccing a run.
+- `autopilot` (alias: `/autopilot`, `$autopilot`): Optional explicit mode for one bounded spec/plan/implement/verify/report pass with checkpoint commits and review packet.
+- `goal`: Route broad, open-ended goals before Discovery.
+- `brainstorm`: Structured divergent & convergent ideation without creating running IDs.
+- `research`: Conduct deep codebase or web research with source-backed citations.
+- `debug`: Root cause investigation before or during implementation without editing code.
+- `prd`: Product Requirements Document drafting before delivery commitment.
+- `issue-triage`: Intake, categorize, and prioritize incoming issues and bug reports.
+- `security-review`: High-severity vulnerability and security review.
+- `wiki`: Knowledge base management and ingestion under `devflow/wiki/`.
+- `check-for-updates`: Verify or upgrade DevFlow setup.
+- `help`: Routing and process assistance across DevFlow workflows.
+
+## Invocation Reference
+
+| Stage / Command | Normal Name | Semantic Alias | OpenAI Codex | Slash Command | Natural Language |
+| :--- | :--- | :--- | :--- | :--- | :--- |
+| **Setup (Fresh)**| `onboard` | `setup` | `$onboard`, `$setup` | `/onboard` | "onboard project", "setup devflow" |
+| **Adopt (Exist)**| `adopt` | `bootstrap` | `$adopt`, `$bootstrap` | `/adopt` | "adopt codebase", "bootstrap devflow" |
+| **Diagnostics** | `doctor` | `health` | `$doctor`, `$health` | `/doctor` | "doctor check", "diagnose devflow" |
+| **Manual QA** | `try` | `manual-test` | `$try` | `/try` | "how to try", "where to click", "manual test guide" |
+| **Reversal** | `rollback` | `revert` | `$rollback` | `/rollback` | "rollback run", "undo feature", "plan reversal" |
+| **CI Setup** | `ci` | `github-actions`| `$ci` | `/ci` | "setup ci", "create github actions", "add verify workflow" |
+| **Pre-Check** | `brief` | `preview-scope`| `$brief` | `/brief` | "brief feature", "check next scope", "preview run" |
+| **Autopilot** | `autopilot` | `auto-loop` | `$autopilot` | `/autopilot` | "run autopilot", "autopilot feature", "start auto loop" |
+| **Stage 00** | `00-discover` | `discover` | `$00-discover`, `$discover` | `/00-discover` | "start discovery", "explore request" |
+| **Stage 10** | `10-define` | `define` | `$10-define`, `$define` | `/10-define` | "define run scope", "allocate run" |
+| **Stage 20** | `20-spec` | `spec` | `$20-spec`, `$spec` | `/20-spec` | "write spec", "create delivery contract" |
+| **Stage 30** | `30-plan` | `plan` | `$30-plan`, `$plan` | `/30-plan` | "plan tasks", "breakdown plan" |
+| **Stage 40** | `40-implement` | `implement` | `$40-implement`, `$implement` | `/40-implement` | "implement step", "build task" |
+| **Stage 50** | `50-verify` | `verify` | `$50-verify`, `$verify` | `/50-verify` | "verify QA", "run validation" |
+| **Stage 60** | `60-report` | `report` | `$60-report`, `$report` | `/60-report` | "generate report", "summarize run" |
+| **Stage 70** | `70-release` | `release` | `$70-release`, `$release` | `/70-release` | "package release", "prepare PR/deploy" |
+| **Router** | `devflow` | `status` | `$devflow`, `$status` | `/devflow` | "what to do next", "check progress" |
 
 ## Mainline Rules
 
@@ -50,9 +130,9 @@ Unused adapter families can be removed. Codex and Antigravity projects keep `.ag
 3. If a command is not a true mainline state, do not give it a number.
 4. Companion commands may be suggested by a mainline workflow but do not replace that workflow.
 
-## Verification & Commands
+## Commands
 
-- Verify framework integrity: `npm run check`
-- Static contract check: `npm run check:static`
-- Test installer package: `npm test`
-- Package smoke test: `npm run test:package`
+- Dev Server: `npm run dev`
+- Build: `npm run build`
+- Test: `npm test`
+- Verify: `npm run check` (Run `/onboard` to auto-configure)

package/template/devflow/context/coding-standards.md

@@ -1,19 +1,27 @@
-# Coding Standards & Guidelines
+# Coding Standards
 
-General engineering standards for code, tests, and documentation.
+> Project conventions and rules to follow during development.
+> Run `/onboard` (or `/adopt` for existing codebases) to tune these standards to your specific stack.
 
-## Code Quality
+## Architecture and Conventions
 
-- Write clear, self-documenting code.
-- Avoid unnecessary complexity (prefer simple solutions over indirect abstractions).
-- Maintain type safety and static validation across module boundaries.
+- Write clean, modular, and maintainable code with clear single responsibilities.
+- Prefer TypeScript and explicit interfaces where available.
+- Keep dependencies lean and justified.
 
-## Testing & Verification
+## Code Organization & Style
 
-- Every change in `/40-Implement` must be verified in `/50-Verify`.
-- Prefer test-driven evidence and automated scripts where applicable.
+- Structure source code following framework-native conventions.
+- Keep functions focused and avoid deeply nested logic.
+- Use consistent naming conventions (camelCase for functions/variables, PascalCase for components/types).
 
-## Git & Commits
+## Error Handling & Security
 
-- Commit messages follow imperative summary format.
-- Create small, reviewed, and self-contained commits.
+- Handle errors explicitly and provide meaningful error messages.
+- Never hardcode credentials, secrets, or API keys in source code.
+- Sanitize and validate all user inputs.
+
+## Testing & Quality
+
+- Follow the TDD workflow for behavior-changing code units.
+- Run tests and linting before completing features or fixes.

package/template/devflow/context/current-stage.md

@@ -3,4 +3,5 @@
 - **Active Discovery ID**: None
 - **Active Running ID**: None
 - **Current Stage**: Idle
-- **Last Updated**: 2026-08-17
+- **Last Completed Run**: None
+- **Last Updated**: -

package/template/devflow/context/findings.md

@@ -1,13 +1,9 @@
-# Audit Findings Ledger
+# Findings Ledger
 
-Summary of audit findings, quality checks, security bugs, and debt tracked across DevFlow runs.
+> Review findings raised by `/security-review` or QA audits.
+> Resolved findings are tracked with durable IDs.
 
-## Open Findings
+- **Total Open P0/P1**: 0
+- **Total Tracked**: 0
 
-| ID | Severity | Category | Title | Discovered Run | Status |
-| :- | :--- | :--- | :--- | :--- | :--- |
-
-## Resolved Findings
-
-| ID | Severity | Category | Title | Resolved Run | Date |
-| :- | :--- | :--- | :--- | :--- | :--- |
+_No findings recorded._

package/template/devflow/context/project-overview.md

@@ -1,20 +1,19 @@
 # Project Overview
 
-Primary source of truth for the project context, architecture, tech stack, and active DevFlow stage status.
+> **DevFlow Context Source of Truth.**
+> Single AI-facing source of truth for project architecture, stack, and shipped capabilities.
+> Run `/onboard` (for fresh projects) or `/adopt` (for existing codebases) to populate this file automatically.
 
-## Application Summary
+## 1. Project Summary
 
-- **Project Name**: [Project Name]
-- **Goal**: [Project Goal Description]
-- **Target Audience**: [Target Users]
+- **Name**: [Project Name]
+- **Description**: [One-line summary of project purpose]
+- **Primary Stack**: [Framework / Language / Runtime]
 
-## Tech Stack
+## 2. Architecture & Modules
 
-- **Frontend**: [Framework / Language]
-- **Backend**: [Framework / Database]
-- **Deployment**: [Platform / Infrastructure]
+- `src/` - Core application source code
 
-## DevFlow Workspaces
+## 3. Shipped Capabilities
 
-- **Active Discovery ID**: None
-- **Active Running ID**: None
+- None recorded yet. Run `/onboard` or `/adopt` to initialize.