@slope-dev/slope 1.59.2 → 1.61.0

package/templates/claude-code/rules/sprint-checklist.md

@@ -7,22 +7,25 @@ The SLOPE framework organizes sprint work into a hierarchy of routines, mirrorin
 Before starting a new phase or project:
 
 1. **Define the vision** — What does the end state look like? Document in a vision doc
-2. **Build the roadmap** — Create `docs/backlog/roadmap.json` with sprints, dependencies, and phases
-3. **Run `slope roadmap validate`** — Check for structural issues, dependency cycles, numbering gaps
-4. **Run `slope roadmap review`** — Automated architect review: scope balance, critical path, bottlenecks
-5. **Identify the critical path** — Run `slope roadmap show` to see the dependency graph and parallel tracks
-6. **Plan parallel tracks** — If sprints can run concurrently, plan for multi-agent execution
+2. **Build the roadmap** — Edit declared YAML bundles when `docs/roadmap/project.yaml` exists; otherwise create `docs/backlog/roadmap.json`
+3. **Compile modular sources** — Run `slope roadmap compile`, `slope roadmap validate-sources`, and `slope roadmap compile --check`
+4. **Run `slope roadmap validate`** — Check for structural issues, dependency cycles, numbering gaps
+5. **Run `slope roadmap review`** — Automated architect review: scope balance, critical path, bottlenecks
+6. **Identify the critical path** — Run `slope roadmap show` to see the dependency graph and parallel tracks
+7. **Plan parallel tracks** — If sprints can run concurrently, plan for multi-agent execution
 
 ## Pre-Round Routine (Sprint Start)
 
 Before writing any code in a new sprint:
 
-1. **Run `slope briefing`** — Single command that outputs handicap snapshot, hazard index, nutrition alerts, filtered gotchas, and session continuity
+1. **Run `slope now`** — Discover the current sprint and next action
+2. **Run `slope roadmap focus --sprint=N`** — Use the discovered sprint to load bounded context before full history
+3. **Run `slope briefing`** — Single command that outputs handicap snapshot, hazard index, nutrition alerts, filtered gotchas, and session continuity
    - Use `--categories=testing,api` or `--keywords=migration` to filter for the sprint's work area
-2. **Verify previous scorecard exists** — If the last sprint's scorecard wasn't created, create it now
-3. **Branch hygiene check** — `git branch -a` to confirm no stale branches remain
-4. **Gap analysis** (if touching API or schema) — Read relevant docs and compare against implementation before writing code
-5. **Set par and slope** — Par from ticket count (1-2=3, 3-4=4, 5+=5), slope from complexity factors
+4. **Verify previous scorecard exists** — If the last sprint's scorecard wasn't created, create it now
+5. **Branch hygiene check** — `git branch -a` to confirm no stale branches remain
+6. **Gap analysis** (if touching API or schema) — Read relevant docs and compare against implementation before writing code
+7. **Set par and slope** — Par from ticket count (1-2=3, 3-4=4, 5+=5), slope from complexity factors
 
 ## Pre-Shot Routine (Per-Ticket, Before Code)
 

package/templates/codex/plugins/slope/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "slope",
-  "version": "1.59.2",
+  "version": "1.61.0",
   "description": "SLOPE sprint tracking, guard hooks, and Codex workflow skills.",
   "author": {
     "name": "SLOPE",

package/templates/codex/plugins/slope/skills/slope-retro/SKILL.md

@@ -20,7 +20,7 @@ Use this after the PR is merged, or when the user asks to preserve lessons from
 2. Persist the retro:
    `slope retro post-merge --sprint=<N> --pr=<PR> --summary="<summary>" --learning="<learning>" --hazard="<hazard>" --follow-up="<follow-up>"`
 3. Repeat `--learning`, `--hazard`, and `--follow-up` as needed.
-4. Use `--learning=project:8:<text>` or another `category[:weight]:text` prefix when the memory category matters.
+4. Use `--learning=project:8:<text>` or another supported `category[:weight]:text` prefix when the memory category matters. Supported categories are `workflow`, `style`, `project`, `hazard`, and `other`; `process` is accepted as an alias for `workflow`; weight must be 1-10.
 
 ## Verify
 

package/templates/codex/plugins/slope/skills/slope-sprint/SKILL.md

@@ -9,10 +9,11 @@ Use these commands from the repository root.
 
 ## Inspect
 
-1. Run `slope sprint status`.
-2. If no sprint is active, run `slope next` and `slope briefing --sprint=<next>`.
-3. If a sprint is active, run `slope briefing --sprint=<active>` before editing.
-4. If the user asks for a roadmap interview or planning input, run `slope roadmap interview` or `slope roadmap interview --agent`; MCP agents can also search `module: "init"`.
+1. Run `slope now` to discover the active or next sprint and its next action.
+2. Run `slope roadmap focus --sprint=<discovered>` before loading full roadmap history.
+3. Run `slope sprint status` when operational gate or rollover detail is needed.
+4. Run `slope briefing --sprint=<discovered>` before editing.
+5. If the user asks for a roadmap interview or planning input, run `slope roadmap interview` or `slope roadmap interview --agent`; MCP agents can also search `module: "init"`.
 
 ## Start Or Claim
 

package/templates/cursor/rules/slope-sprint-checklist.mdc

@@ -12,20 +12,23 @@ The SLOPE framework organizes sprint work into a hierarchy of routines, mirrorin
 
 Before starting a new phase or project:
 
-1. **Build the roadmap** — Create `docs/backlog/roadmap.json` with sprints, dependencies, and phases
-2. **Run `slope roadmap validate`** — Check for dependency cycles, numbering gaps
-3. **Run `slope roadmap review`** — Scope balance, critical path, bottlenecks
-4. **Run `slope roadmap show`** — Dependency graph and parallel tracks
+1. **Build the roadmap** — Edit declared YAML bundles when `docs/roadmap/project.yaml` exists; otherwise create `docs/backlog/roadmap.json`
+2. **Compile modular sources** — Run `slope roadmap compile`, `slope roadmap validate-sources`, and `slope roadmap compile --check`
+3. **Run `slope roadmap validate`** — Check for dependency cycles, numbering gaps
+4. **Run `slope roadmap review`** — Scope balance, critical path, bottlenecks
+5. **Run `slope roadmap show`** — Dependency graph and parallel tracks
 
 ## Pre-Round Routine (Sprint Start)
 
 Before writing any code in a new sprint:
 
-1. **Run `slope briefing`** — Outputs handicap snapshot, hazard index, nutrition alerts, filtered gotchas, and session continuity
+1. **Run `slope now`** — Discover the current sprint and next action
+2. **Run `slope roadmap focus --sprint=N`** — Use the discovered sprint to load bounded context before full history
+3. **Run `slope briefing`** — Outputs handicap snapshot, hazard index, nutrition alerts, filtered gotchas, and session continuity
    - Use `--categories=testing,api` or `--keywords=migration` to filter for the sprint's work area
-2. **Verify previous scorecard exists** — If the last sprint's scorecard wasn't created, create it now
-3. **Branch hygiene check** — `git branch -a` to confirm no stale branches remain
-4. **Set par and slope** — Par from ticket count (1-2=3, 3-4=4, 5+=5), slope from complexity factors
+4. **Verify previous scorecard exists** — If the last sprint's scorecard wasn't created, create it now
+5. **Branch hygiene check** — `git branch -a` to confirm no stale branches remain
+6. **Set par and slope** — Par from ticket count (1-2=3, 3-4=4, 5+=5), slope from complexity factors
 
 ## Pre-Shot Routine (Per-Ticket, Before Code)
 

package/templates/generic/SLOPE-CHECKLIST.md

@@ -1,15 +1,18 @@
 # SLOPE Sprint Checklist
 
 ## Pre-Tournament (Course Strategy)
-1. Build roadmap in `docs/backlog/roadmap.json`
-2. Run `slope roadmap validate` — check dependencies and structure
-3. Run `slope roadmap review` — scope balance, critical path, bottlenecks
-4. Run `slope roadmap show` — view dependency graph
+1. Build the roadmap in declared YAML bundles when `docs/roadmap/project.yaml` exists; otherwise use `docs/backlog/roadmap.json`
+2. For modular sources, run `slope roadmap compile`, `slope roadmap validate-sources`, and `slope roadmap compile --check`
+3. Run `slope roadmap validate` — check dependencies and structure
+4. Run `slope roadmap review` — scope balance, critical path, bottlenecks
+5. Run `slope roadmap show` — view dependency graph
 
 ## Pre-Round (Sprint Start)
-1. Run `slope briefing` — handicap, hazards, gotchas, session continuity
-2. Verify previous scorecard exists
-3. Set par (1-2 tickets=3, 3-4=4, 5+=5) and slope factors
+1. Run `slope now` — discover the current sprint and next action
+2. Run `slope roadmap focus --sprint=N` — bounded context for the discovered sprint
+3. Run `slope briefing` — handicap, hazards, gotchas, session continuity
+4. Verify previous scorecard exists
+5. Set par (1-2 tickets=3, 3-4=4, 5+=5) and slope factors
 
 ## Per-Ticket
 - **Before:** Select club (driver/long_iron/short_iron/wedge/putter), scan hazards
@@ -18,8 +21,9 @@
 ## Post-Hole (Sprint End)
 1. Build scorecard JSON, run `slope validate`
 2. Update common-issues with new patterns
-3. Run `slope review` for markdown output
-4. Run `slope card` for handicap trends
+3. Log recurring workaround/codification candidates with `slope review findings add --type=workaround --recurs --cost=s|m|l --description="..."`
+4. Run `slope review` for markdown output
+5. Run `slope card` for handicap trends
 
 ## Commit Discipline
 - Commit after each file, feature, migration, or bug fix

package/templates/pi/skills/post-sprint.md

@@ -55,6 +55,7 @@ Run `slope review` to generate the sprint review markdown. Share the output with
 If any new recurring patterns were encountered during this sprint:
 - Check `.slope/common-issues.json` for existing patterns
 - Add new patterns or update `sprints_hit` arrays for existing ones
+- Sweep for recurring workarounds that were routed around in-flow. Log structural ones with `slope review findings add --type=workaround --recurs --cost=s|m|l --description="..."`.
 
 ### 6. Roadmap status (auto-updated)
 
@@ -69,4 +70,5 @@ Ask the user if they'd like to create a PR. If yes, create one with the sprint r
 - Always run `slope validate` after creating the scorecard — never skip this
 - The scorecard must match the actual work done (commits), not the plan
 - Record hazards honestly — they feed the handicap system and improve future guidance
+- Log recurring workaround/codification candidates; one-offs can stay out of the ledger
 - If the sprint had review findings, run `slope review amend` after adding findings

package/templates/pi/skills/start-sprint.md

@@ -16,22 +16,27 @@ Run the complete pre-sprint routine: verify prior sprint hygiene, get briefing,
 ### 1. Determine sprint number
 
 - If a number was provided as an argument, use it
-- Otherwise, run `slope next` to auto-detect the next sprint number
+- Otherwise, run `slope now` and use its active or next sprint; use `slope next` only if no sprint is reported
+- Treat the sprint number as the current SLOPE work unit. It may be a time-boxed interval or a scope-based agent milestone.
 
-### 2. Verify prior sprint scorecard
+### 2. Load bounded roadmap context
+
+Run `slope roadmap focus --sprint=N` for the discovered sprint before loading full roadmap history.
+
+### 3. Verify prior sprint scorecard
 
 Check that the previous sprint's scorecard exists at `docs/retros/sprint-{N-1}.json`:
 - If missing, **stop and create it first** using `/skill:post-sprint`
 - If it exists, continue
 - Note: the sprint-completion guard also enforces this — PR creation is blocked without a scorecard
 
-### 3. Branch hygiene
+### 4. Branch hygiene
 
 - Run `git branch` to check for stale branches from prior sprints
 - If stale branches exist, warn the user
 - Create a new feature branch: `feat/sprint-{N}-<theme-slug>`
 
-### 4. Run briefing
+### 5. Run briefing
 
 Run `slope briefing` to get:
 - Handicap snapshot (rolling performance stats)
@@ -44,7 +49,7 @@ If you know the sprint's work area, add filters:
 slope briefing --categories=<area> --keywords=<topic>
 ```
 
-### 5. Start sprint with workflow engine
+### 6. Start sprint with workflow engine
 
 Run `slope sprint run --workflow=sprint-standard --var sprint_id=S{N}` to start a workflow-controlled sprint.