@jakkrichm/create-nexus-devflow 2.0.0 → 2.0.1

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

@@ -3,146 +3,146 @@ name: goal
 description: Goal workflow
 ---
 
----
-description: Goal Router - Route a high-level goal into the correct DevFlow 2.0 path and record recommendation metrics.
----
-# Phase 05: Goal Router
-
-Route a high-level `/goal` request into the most appropriate DevFlow path.
-
-## Usage
-
-```text
-/goal {GOAL_DESCRIPTION}
-```
-
-Local CLI equivalent:
-
-```powershell
-npm run goal -- --goal "Implement goal command" --max-turns 30 --parallel
-npm run goal -- goal "Implement goal command" max-turns 30 parallel
-```
-
-## Purpose
-
-The goal router turns an open-ended request into a routed DevFlow recommendation plan.
-
-It should:
-
-- classify the goal into the right path
-- decompose large goals into worker-sized chunks
-- recommend the exact next command
-- record routing decisions, turn budget, and context notes in a session log
-
-The current goal runner is a routing and recommendation surface. It does not replace the mainline workflow or silently execute the full delivery lifecycle.
-
-## Boss-Worker Roles
-
-- `prp-core-boss` owns routing, decomposition, turn budgets, validation gates, and final synthesis.
-- `prp-core-worker` owns focused implementation or analysis subtasks assigned by the Boss.
-- Specialist agents may still be invoked with `Agent` when a task needs deeper domain expertise.
-
-## Flow Routing
-
-The Boss first classifies the request into one of these paths:
-
-| Flow | Use When | Typical Next Step |
-| :--- | :--- | :--- |
+---
+description: Goal Router - Route a high-level goal into the correct DevFlow 2.0 path and record recommendation metrics.
+---
+# Phase 05: Goal Router
+
+Route a high-level `/goal` request into the most appropriate DevFlow path.
+
+## Usage
+
+```text
+/goal {GOAL_DESCRIPTION}
+```
+
+Local CLI equivalent:
+
+```powershell
+npm run goal -- --goal "Implement goal command" --max-turns 30 --parallel
+npm run goal -- goal "Implement goal command" max-turns 30 parallel
+```
+
+## Purpose
+
+The goal router turns an open-ended request into a routed DevFlow recommendation plan.
+
+It should:
+
+- classify the goal into the right path
+- decompose large goals into worker-sized chunks
+- recommend the exact next command
+- record routing decisions, turn budget, and context notes in a session log
+
+The current goal runner is a routing and recommendation surface. It does not replace the mainline workflow or silently execute the full delivery lifecycle.
+
+## Boss-Worker Roles
+
+- `prp-core-boss` owns routing, decomposition, turn budgets, validation gates, and final synthesis.
+- `prp-core-worker` owns focused implementation or analysis subtasks assigned by the Boss.
+- Specialist agents may still be invoked with `Agent` when a task needs deeper domain expertise.
+
+## Flow Routing
+
+The Boss first classifies the request into one of these paths:
+
+| Flow | Use When | Typical Next Step |
+| :--- | :--- | :--- |
 | DevFlow Mainline | New feature, bug, test, docs, migration, or refactor requests. | `/00-Discover`, which owns the delivery decision |
 | PRD / Spec Orchestration | Product ideas or requirement-heavy planning before a Discovery ID exists. | `/00-Discover`, likely routing to `PRD` |
 | Brainstorm Flow | Early ambiguous ideas that need options and tradeoff analysis. | `/00-Discover`, likely routing to `Brainstorm` |
 | Research Flow | External facts, docs, codebase evidence, or feasibility proof are needed. | `/00-Discover`, likely routing to `Research` |
 | RCA / Debug Flow | Failures, errors, regressions, or investigation-heavy bug reports. | `/00-Discover`, likely routing to `Debug` |
-
-## Process
-
-1. Parse the goal text and runtime config.
-2. Select a flow path and record the reasoning.
-3. Estimate complexity and split large goals into worker-sized tasks.
-4. Recommend the relevant DevFlow commands in the correct order.
-5. Track turns by phase and stop when the configured `max-turns` budget is reached.
-6. Run validation gates appropriate to the selected flow.
-7. Add lightweight context usage notes when the runtime or operator can provide them.
-8. Save a structured session report.
-
-## Log Contract
-
-Session logs are written to:
-
-```text
-devflow/runs/goal-sessions/session-{goal_id}.json
-devflow/runs/goal_latest_session.json
-devflow/runs/goal_execution_log.json
-```
-
-Each log includes:
-
-- `goal_id`
-- `goal_description`
-- `status`
-- `execution_mode`
-- `config`
-- `metrics`
-- `context_usage`
-- `flow_selected`
-- `tasks_decomposed`
-- `execution_steps`
-- `recommended_commands`
-
-### Context Usage Notes
-
-`context_usage` is intentionally manual and optional until the runtime exposes exact token telemetry. Use it to capture:
-
-- `context_loaded`
-- `files_read`
-- `artifacts_read`
-- `token_usage`
-- `optimization_notes`
-
-## Validation
-
-After changing goal runner behavior, run:
-
-```powershell
-npm run validate
-node .agent/scripts/test-goal-runner.mjs
-npm run goal -- goal "Create a small test task" max-turns 15 dry-run
-```
-
-## Output
-
-Report:
-
-- selected flow
-- task decomposition summary
-- session log path
-- recommended next command
-- key assumptions or routing risks
-
-## Relationship To DevFlow 2.0
-
-- Classification: Companion command
-- Mainline status: Not a numbered stage
+
+## Process
+
+1. Parse the goal text and runtime config.
+2. Select a flow path and record the reasoning.
+3. Estimate complexity and split large goals into worker-sized tasks.
+4. Recommend the relevant DevFlow commands in the correct order.
+5. Track turns by phase and stop when the configured `max-turns` budget is reached.
+6. Run validation gates appropriate to the selected flow.
+7. Add lightweight context usage notes when the runtime or operator can provide them.
+8. Save a structured session report.
+
+## Log Contract
+
+Session logs are written to:
+
+```text
+devflow/runs/goal-sessions/session-{goal_id}.json
+devflow/runs/goal_latest_session.json
+devflow/runs/goal_execution_log.json
+```
+
+Each log includes:
+
+- `goal_id`
+- `goal_description`
+- `status`
+- `execution_mode`
+- `config`
+- `metrics`
+- `context_usage`
+- `flow_selected`
+- `tasks_decomposed`
+- `execution_steps`
+- `recommended_commands`
+
+### Context Usage Notes
+
+`context_usage` is intentionally manual and optional until the runtime exposes exact token telemetry. Use it to capture:
+
+- `context_loaded`
+- `files_read`
+- `artifacts_read`
+- `token_usage`
+- `optimization_notes`
+
+## Validation
+
+After changing goal runner behavior, run:
+
+```powershell
+npm run validate
+node .agent/scripts/test-goal-runner.mjs
+npm run goal -- goal "Create a small test task" max-turns 15 dry-run
+```
+
+## Output
+
+Report:
+
+- selected flow
+- task decomposition summary
+- session log path
+- recommended next command
+- key assumptions or routing risks
+
+## Relationship To DevFlow 2.0
+
+- Classification: Companion command
+- Mainline status: Not a numbered stage
 - Typical entry points: broad goals before a Discovery ID exists
 - Typical handoff target: `/00-Discover`, with a likely companion route recorded as guidance rather than executed outside Discover
-
-## Sources
-
-- `AGENTS.md`
-- `.agent/scripts/goal-runner.mjs`
+
+## Sources
+
+- `AGENTS.md`
+- `.agent/scripts/goal-runner.mjs`
 - Related commands: `/00-Discover`, `Brainstorm`, `Research`, `PRD`, `Spec-Orchestrate`, `Debug`
-
-## Next Workflow Recommendation
-
-- **Primary**: the first command listed in `recommended_commands`
-- **Why**: `Goal` exists to route broad intent into the correct DevFlow 2.0 entry point
-- **Alternatives**:
+
+## Next Workflow Recommendation
+
+- **Primary**: the first command listed in `recommended_commands`
+- **Why**: `Goal` exists to route broad intent into the correct DevFlow 2.0 entry point
+- **Alternatives**:
   - `/00-Discover "{goal}"` for all new work; Discover chooses Brainstorm, PRD, Research, Debug, or direct decision
   - `/10-Define {discovery_id}` only after an approved Proceed decision
   - `/20-Spec {running_id}` only for an existing approved delivery run
-
-## Wiki Update Recommendation
-
-- Update the wiki only when the goal-routing session reveals a durable pattern, intake heuristic, or onboarding note worth reusing.
-- If the output is only a one-off routing decision, do not create or update wiki pages.
-
+
+## Wiki Update Recommendation
+
+- Update the wiki only when the goal-routing session reveals a durable pattern, intake heuristic, or onboarding note worth reusing.
+- If the output is only a one-off routing decision, do not create or update wiki pages.
+