@mrciphersmith/keryx 0.2.72 → 0.2.74

package/src/gdskills/bundled/skills/planning/planner/SKILL.codex.md

@@ -1,18 +1,14 @@
 ---
-name: gproject-planner
-description: "Generates roadmap, milestones, task breakdown with dependency graph and effort estimates from approved PRD. Use when: dispatched by gproject-orchestrator Phase 6."
-triggers:
-  - "gproject-planner: generate roadmap"
-  - "Dispatched by gproject-orchestrator Phase 6"
+name: planner
+description: >
+  Generates roadmap, milestones, task breakdown, and dependency graph from PRD.
+  Use when: dispatched by gproject-orchestrator Phase 6.
+  NOT for: direct user invocation.
 metadata:
-  author: "MrCipherSmith"
-  version: "1.0.0"
-  category: "planning"
+  version: 1.0.0
   compatible_harnesses: "cursor,codex,zed,opencode"
-license: "MIT"
 ---
 
-
 # gproject-planner
 
 ## Purpose
@@ -31,3 +27,166 @@ to feed into job-orchestrator or task-implementer.
 | 4 | P0 user stories MUST be in Milestone 1 |
 | 5 | Each milestone MUST be independently deployable / demonstrable |
 | 6 | Infrastructure and setup tasks come before feature tasks |
+
+---
+
+## Input Contract
+
+```yaml
+task: "Generate roadmap and task breakdown"
+input_artifacts:
+  - .metaproject/jobs/<job>/artifacts/prd.md
+  - .metaproject/jobs/<job>/artifacts/architecture.md
+decisions_so_far:
+  D_level: "..."
+  D_frontend: "..."
+  D_backend: "..."
+  # All relevant decisions
+```
+
+## Output Contract
+
+```yaml
+status: "DONE" | "NEEDS_CONTEXT"
+summary: "<3-5 sentences: milestone count, total tasks, critical path duration>"
+new_decisions:
+  D_milestones: ["<M1 name>", "<M2 name>", ...]
+  D_estimated_duration: "<range>"
+  D_critical_path: "<list of blocking tasks>"
+artifact_path: ".metaproject/jobs/<job>/artifacts/roadmap.md"
+```
+
+---
+
+## Workflow
+
+### Step 1: Decompose User Stories into Tasks
+
+For each user story, break into implementation tasks:
+
+```yaml
+- task_id: "T-001"
+  title: "<specific task>"
+  user_story: "US-001"
+  layer: "frontend | backend | database | infra | testing"
+  type: "setup | feature | integration | test | docs"
+  estimate:
+    optimistic: "<time>"
+    realistic: "<time>"
+    pessimistic: "<time>"
+  depends_on: ["T-000"]  # or [] if no deps
+  acceptance_criteria:
+    - "<from user story, scoped to this task>"
+  files_likely_affected:
+    - "<file path or module>"
+```
+
+### Step 2: Identify Dependencies
+
+Build dependency graph:
+- Infrastructure tasks → before all feature tasks
+- Database schema → before backend → before frontend
+- Auth setup → before any authenticated feature
+- Shared components → before pages that use them
+
+Verify: no cycles in dependency graph.
+
+### Step 3: Group into Milestones
+
+Each milestone:
+- Has a clear deliverable (demo-able, deployable)
+- Contains all P0 stories it covers (no half-done P0 at milestone end)
+- Ends with a verification checkpoint
+
+Typical milestone structure:
+
+**M0: Foundation**
+- Project setup, tooling, CI/CD, dev environment
+- Database schema initial migration
+- Auth skeleton
+- Deploy pipeline to staging
+
+**M1: Core (P0 features)**
+- All P0 user stories
+- Core API endpoints
+- Core UI flows
+- Integration tests for critical paths
+
+**M2: Complete (P1 features)**
+- P1 user stories
+- Polish, edge cases
+- Performance optimization
+- Full test coverage
+
+**M3: Launch-Ready (if production level)**
+- P2 features (selected)
+- Security hardening
+- Monitoring, alerting
+- Documentation
+- Load testing
+
+### Step 4: Estimate Critical Path
+
+Identify the longest dependency chain and estimate total duration.
+Flag tasks that block the most other tasks.
+
+### Step 5: Write Roadmap
+
+Write `artifacts/roadmap.md`:
+
+```markdown
+# Roadmap: <Project/Task Name>
+
+## Overview
+- **Milestones**: <count>
+- **Total tasks**: <count>
+- **Estimated duration**: <optimistic> — <realistic> — <pessimistic>
+- **Critical path**: <list of blocking tasks>
+
+## Milestone 0: Foundation
+**Deliverable**: <what can be demonstrated>
+**Duration estimate**: <range>
+
+### Tasks
+| ID | Title | Layer | Depends On | Estimate | Story |
+|----|-------|-------|-----------|----------|-------|
+| T-001 | <title> | infra | — | <range> | — |
+| T-002 | <title> | database | T-001 | <range> | — |
+
+## Milestone 1: Core
+**Deliverable**: <what can be demonstrated>
+**Duration estimate**: <range>
+
+### Tasks
+| ID | Title | Layer | Depends On | Estimate | Story |
+|----|-------|-------|-----------|----------|-------|
+| T-010 | <title> | backend | T-002 | <range> | US-001 |
+
+## ...
+
+## Dependency Graph (summary)
+<textual description of key dependency chains>
+T-001 → T-002 → T-010 → T-015 (critical path)
+T-001 → T-003 → T-011 (parallel track)
+
+## Risk-Adjusted Timeline
+| Scenario | Duration | Assumptions |
+|----------|---------|-------------|
+| Optimistic | <time> | No blockers, all estimates hold |
+| Realistic | <time> | Normal friction, 1-2 minor blockers |
+| Pessimistic | <time> | Major unknowns surface, rework needed |
+
+## Parallelization Opportunities
+<Which tasks can run simultaneously — useful for team or multi-agent execution>
+
+## Integration with job-orchestrator
+<How to feed this roadmap into job-orchestrator for automated implementation>
+- Each milestone maps to a job-orchestrator run
+- Tasks within a milestone map to issue-analyzer output format
+- Dependency order maps to wave-based execution
+```
+
+### Step 6: Return Summary
+
+Compact summary: milestone count, task count, critical path duration,
+biggest scheduling risk.

package/src/gdskills/bundled/skills/planning/planner/SKILL.cursor.md

@@ -1,18 +1,14 @@
 ---
-name: gproject-planner
-description: "Generates roadmap, milestones, task breakdown with dependency graph and effort estimates from approved PRD. Use when: dispatched by gproject-orchestrator Phase 6."
-triggers:
-  - "gproject-planner: generate roadmap"
-  - "Dispatched by gproject-orchestrator Phase 6"
+name: planner
+description: >
+  Generates roadmap, milestones, task breakdown, and dependency graph from PRD.
+  Use when: dispatched by gproject-orchestrator Phase 6.
+  NOT for: direct user invocation.
 metadata:
-  author: "MrCipherSmith"
-  version: "1.0.0"
-  category: "planning"
+  version: 1.0.0
   compatible_harnesses: "cursor,codex,zed,opencode"
-license: "MIT"
 ---
 
-
 # gproject-planner
 
 ## Purpose
@@ -31,3 +27,166 @@ to feed into job-orchestrator or task-implementer.
 | 4 | P0 user stories MUST be in Milestone 1 |
 | 5 | Each milestone MUST be independently deployable / demonstrable |
 | 6 | Infrastructure and setup tasks come before feature tasks |
+
+---
+
+## Input Contract
+
+```yaml
+task: "Generate roadmap and task breakdown"
+input_artifacts:
+  - .metaproject/jobs/<job>/artifacts/prd.md
+  - .metaproject/jobs/<job>/artifacts/architecture.md
+decisions_so_far:
+  D_level: "..."
+  D_frontend: "..."
+  D_backend: "..."
+  # All relevant decisions
+```
+
+## Output Contract
+
+```yaml
+status: "DONE" | "NEEDS_CONTEXT"
+summary: "<3-5 sentences: milestone count, total tasks, critical path duration>"
+new_decisions:
+  D_milestones: ["<M1 name>", "<M2 name>", ...]
+  D_estimated_duration: "<range>"
+  D_critical_path: "<list of blocking tasks>"
+artifact_path: ".metaproject/jobs/<job>/artifacts/roadmap.md"
+```
+
+---
+
+## Workflow
+
+### Step 1: Decompose User Stories into Tasks
+
+For each user story, break into implementation tasks:
+
+```yaml
+- task_id: "T-001"
+  title: "<specific task>"
+  user_story: "US-001"
+  layer: "frontend | backend | database | infra | testing"
+  type: "setup | feature | integration | test | docs"
+  estimate:
+    optimistic: "<time>"
+    realistic: "<time>"
+    pessimistic: "<time>"
+  depends_on: ["T-000"]  # or [] if no deps
+  acceptance_criteria:
+    - "<from user story, scoped to this task>"
+  files_likely_affected:
+    - "<file path or module>"
+```
+
+### Step 2: Identify Dependencies
+
+Build dependency graph:
+- Infrastructure tasks → before all feature tasks
+- Database schema → before backend → before frontend
+- Auth setup → before any authenticated feature
+- Shared components → before pages that use them
+
+Verify: no cycles in dependency graph.
+
+### Step 3: Group into Milestones
+
+Each milestone:
+- Has a clear deliverable (demo-able, deployable)
+- Contains all P0 stories it covers (no half-done P0 at milestone end)
+- Ends with a verification checkpoint
+
+Typical milestone structure:
+
+**M0: Foundation**
+- Project setup, tooling, CI/CD, dev environment
+- Database schema initial migration
+- Auth skeleton
+- Deploy pipeline to staging
+
+**M1: Core (P0 features)**
+- All P0 user stories
+- Core API endpoints
+- Core UI flows
+- Integration tests for critical paths
+
+**M2: Complete (P1 features)**
+- P1 user stories
+- Polish, edge cases
+- Performance optimization
+- Full test coverage
+
+**M3: Launch-Ready (if production level)**
+- P2 features (selected)
+- Security hardening
+- Monitoring, alerting
+- Documentation
+- Load testing
+
+### Step 4: Estimate Critical Path
+
+Identify the longest dependency chain and estimate total duration.
+Flag tasks that block the most other tasks.
+
+### Step 5: Write Roadmap
+
+Write `artifacts/roadmap.md`:
+
+```markdown
+# Roadmap: <Project/Task Name>
+
+## Overview
+- **Milestones**: <count>
+- **Total tasks**: <count>
+- **Estimated duration**: <optimistic> — <realistic> — <pessimistic>
+- **Critical path**: <list of blocking tasks>
+
+## Milestone 0: Foundation
+**Deliverable**: <what can be demonstrated>
+**Duration estimate**: <range>
+
+### Tasks
+| ID | Title | Layer | Depends On | Estimate | Story |
+|----|-------|-------|-----------|----------|-------|
+| T-001 | <title> | infra | — | <range> | — |
+| T-002 | <title> | database | T-001 | <range> | — |
+
+## Milestone 1: Core
+**Deliverable**: <what can be demonstrated>
+**Duration estimate**: <range>
+
+### Tasks
+| ID | Title | Layer | Depends On | Estimate | Story |
+|----|-------|-------|-----------|----------|-------|
+| T-010 | <title> | backend | T-002 | <range> | US-001 |
+
+## ...
+
+## Dependency Graph (summary)
+<textual description of key dependency chains>
+T-001 → T-002 → T-010 → T-015 (critical path)
+T-001 → T-003 → T-011 (parallel track)
+
+## Risk-Adjusted Timeline
+| Scenario | Duration | Assumptions |
+|----------|---------|-------------|
+| Optimistic | <time> | No blockers, all estimates hold |
+| Realistic | <time> | Normal friction, 1-2 minor blockers |
+| Pessimistic | <time> | Major unknowns surface, rework needed |
+
+## Parallelization Opportunities
+<Which tasks can run simultaneously — useful for team or multi-agent execution>
+
+## Integration with job-orchestrator
+<How to feed this roadmap into job-orchestrator for automated implementation>
+- Each milestone maps to a job-orchestrator run
+- Tasks within a milestone map to issue-analyzer output format
+- Dependency order maps to wave-based execution
+```
+
+### Step 6: Return Summary
+
+Compact summary: milestone count, task count, critical path duration,
+biggest scheduling risk.

package/src/gdskills/bundled/skills/planning/planner/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: gproject-planner
+name: planner
 description: >
   Generates roadmap, milestones, task breakdown, and dependency graph from PRD.
   Use when: dispatched by gproject-orchestrator Phase 6.

package/src/gdskills/bundled/skills/planning/prd-creator/SKILL.codex.md

@@ -1,6 +1,6 @@
 ---
 name: prd-creator
-description: "Transforms unstructured user requests into structured, complete, and testable Product Requirements Documents (PRD). Operates in Direct Mode for user interaction and Orchestrated Mode for pipelined multi-agent workflows."
+description: "Use when a vague or unstructured request needs to be converted into a formal, testable Product Requirements Document."
 triggers:
   - "Create a PRD"
   - "Formulate requirements"
@@ -155,7 +155,7 @@ Then
 - You MUST NOT create a single file in the generic `docs/` root.
 
 **Orchestrated Mode:**
-- The PRD MUST be saved within the active job's directory for traceability: `.metaproject/jobs/<current_job>/`
+- The PRD MUST be saved within the active job's directory for traceability: `<JOBS_ROOT>/<current_job>/`
 - Follow the orchestrator's constraints for exact file naming in the job context.
 
 ---

package/src/gdskills/bundled/skills/planning/prd-creator/SKILL.cursor.md

@@ -1,6 +1,6 @@
 ---
 name: prd-creator
-description: "Transforms unstructured user requests into structured, complete, and testable Product Requirements Documents (PRD). Operates in Direct Mode for user interaction and Orchestrated Mode for pipelined multi-agent workflows."
+description: "Use when a vague or unstructured request needs to be converted into a formal, testable Product Requirements Document."
 triggers:
   - "Create a PRD"
   - "Formulate requirements"
@@ -155,7 +155,7 @@ Then
 - You MUST NOT create a single file in the generic `docs/` root.
 
 **Orchestrated Mode:**
-- The PRD MUST be saved within the active job's directory for traceability: `.metaproject/jobs/<current_job>/`
+- The PRD MUST be saved within the active job's directory for traceability: `<JOBS_ROOT>/<current_job>/`
 - Follow the orchestrator's constraints for exact file naming in the job context.
 
 ---

package/src/gdskills/bundled/skills/planning/prd-creator/SKILL.opencode.md

@@ -1,6 +1,6 @@
 ---
 name: prd-creator
-description: "Transforms unstructured user requests into structured, complete, and testable Product Requirements Documents (PRD). Operates in Direct Mode for user interaction and Orchestrated Mode for pipelined multi-agent workflows."
+description: "Use when a vague or unstructured request needs to be converted into a formal, testable Product Requirements Document."
 triggers:
   - "Create a PRD"
   - "Formulate requirements"
@@ -155,7 +155,7 @@ Then
 - You MUST NOT create a single file in the generic `docs/` root.
 
 **Orchestrated Mode:**
-- The PRD MUST be saved within the active job's directory for traceability: `.metaproject/jobs/<current_job>/`
+- The PRD MUST be saved within the active job's directory for traceability: `<JOBS_ROOT>/<current_job>/`
 - Follow the orchestrator's constraints for exact file naming in the job context.
 
 ---

package/src/gdskills/bundled/skills/planning/prd-creator/SKILL.zed.md

@@ -1,6 +1,6 @@
 ---
 name: prd-creator
-description: "Transforms unstructured user requests into structured, complete, and testable Product Requirements Documents (PRD). Operates in Direct Mode for user interaction and Orchestrated Mode for pipelined multi-agent workflows."
+description: "Use when a vague or unstructured request needs to be converted into a formal, testable Product Requirements Document."
 triggers:
   - "Create a PRD"
   - "Formulate requirements"
@@ -155,7 +155,7 @@ Then
 - You MUST NOT create a single file in the generic `docs/` root.
 
 **Orchestrated Mode:**
-- The PRD MUST be saved within the active job's directory for traceability: `.metaproject/jobs/<current_job>/`
+- The PRD MUST be saved within the active job's directory for traceability: `<JOBS_ROOT>/<current_job>/`
 - Follow the orchestrator's constraints for exact file naming in the job context.
 
 ---

package/src/gdskills/bundled/skills/planning/problem-definer/SKILL.codex.md

@@ -1,18 +1,14 @@
 ---
-name: gproject-problem-definer
-description: "Defines core problems, SMART goals, non-goals, and success metrics from discovery data. Use when: dispatched by gproject-orchestrator Phase 1."
-triggers:
-  - "gproject-problem-definer: define problems and goals"
-  - "Dispatched by gproject-orchestrator Phase 1"
+name: problem-definer
+description: >
+  Defines core problems, goals, non-goals, and success metrics from discovery data.
+  Use when: dispatched by gproject-orchestrator Phase 1.
+  NOT for: direct user invocation.
 metadata:
-  author: "MrCipherSmith"
-  version: "1.0.0"
-  category: "planning"
+  version: 1.0.0
   compatible_harnesses: "cursor,codex,zed,opencode"
-license: "MIT"
 ---
 
-
 # gproject-problem-definer
 
 ## Purpose
@@ -29,3 +25,131 @@ This phase answers: "Why are we doing this?" and "How will we know we succeeded?
 | 3 | Problems MUST be stated from the USER's perspective, not technical |
 | 4 | NEVER introduce solutions in the problem statement |
 | 5 | If discovery brief has low confidence areas, flag them — don't paper over |
+
+---
+
+## Input Contract
+
+```yaml
+task: "Define core problems and goals"
+input_artifacts:
+  - .metaproject/jobs/<job>/artifacts/discovery-brief.md
+decisions_so_far:
+  D_mode: "..."
+  D_domain: "..."
+  D_audience: "..."
+  D_scale_estimate: "..."
+```
+
+## Output Contract
+
+```yaml
+status: "DONE" | "NEEDS_CONTEXT"
+summary: "<3-5 sentences: core problem, primary goal, key constraint>"
+new_decisions:
+  D_core_problems: ["<problem 1>", "<problem 2>"]
+  D_goals: ["<goal 1 + metric>", "<goal 2 + metric>"]
+  D_non_goals: ["<non-goal 1>", "<non-goal 2>", "<non-goal 3>"]
+  D_success_metrics: ["<metric 1>", "<metric 2>"]
+  D_target_users: "<primary persona>"
+artifact_path: ".metaproject/jobs/<job>/artifacts/problem-statement.md"
+```
+
+---
+
+## Workflow
+
+### Step 1: Extract Problems
+
+From discovery brief, identify:
+- What pain points do target users have?
+- What's broken / missing / inefficient?
+- What opportunity exists?
+
+Frame each problem as: "**[User type]** cannot / struggles to **[action]** because **[reason]**, which results in **[consequence]**."
+
+### Step 2: Define Goals (SMART)
+
+For each problem, define a goal:
+- **Specific** — exactly what will change
+- **Measurable** — quantifiable success metric
+- **Achievable** — realistic given constraints
+- **Relevant** — tied to a real problem
+- **Time-bound** — when to evaluate (if applicable)
+
+### Step 3: Define Non-Goals (Critical)
+
+Explicitly state what this project will NOT do. This prevents scope creep
+and aligns expectations. Common categories:
+- Features explicitly excluded from scope
+- User segments not targeted
+- Performance levels not targeted (e.g., "not optimized for 1M+ users")
+- Platforms not supported
+- Integrations not included
+
+### Step 4: Define Success Metrics
+
+For each goal, define how to measure success:
+- Quantitative metrics (response time, conversion rate, error rate)
+- Qualitative metrics (user satisfaction, NPS)
+- Leading indicators (usage frequency, feature adoption)
+
+### Step 5: Write Problem Statement
+
+Write `artifacts/problem-statement.md`:
+
+```markdown
+# Problem Statement: <Project/Task Name>
+
+## Core Problems
+### P1: <Problem Title>
+<User type> cannot <action> because <reason>, resulting in <consequence>.
+**Impact**: <high/medium/low>
+**Evidence**: <from discovery brief>
+
+### P2: ...
+
+## Goals
+### G1: <Goal Title>
+**Statement**: <SMART goal>
+**Success Metric**: <measurable metric>
+**Target**: <specific target value>
+**Measured by**: <how and when>
+
+### G2: ...
+
+## Non-Goals
+### NG1: <Non-Goal>
+**Why excluded**: <rationale>
+
+### NG2: ...
+### NG3: ...
+
+## Target Users
+### Primary Persona
+- **Who**: <description>
+- **Core need**: <what they need most>
+- **Current solution**: <how they solve it today>
+
+### Secondary Persona (if applicable)
+- ...
+
+## Success Criteria
+| Metric | Current State | Target | Measurement Method |
+|--------|--------------|--------|-------------------|
+| <metric> | <baseline or N/A> | <target> | <how to measure> |
+
+## Assumptions & Risks
+| Assumption | Risk if Wrong | Mitigation |
+|-----------|--------------|------------|
+| <assumption> | <impact> | <what to do> |
+
+## Scope Boundary
+**In scope**: <brief list>
+**Out of scope**: <brief list referencing non-goals>
+```
+
+### Step 6: Return Summary
+
+Return compact summary to orchestrator: core problem in one sentence,
+primary goal in one sentence, biggest risk, confidence level.