@slope-dev/slope 1.59.2 → 1.60.0

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/generic/SLOPE-CHECKLIST.md

@@ -18,8 +18,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

@@ -17,6 +17,7 @@ Run the complete pre-sprint routine: verify prior sprint hygiene, get briefing,
 
 - If a number was provided as an argument, use it
 - Otherwise, run `slope next` to auto-detect the next sprint number
+- 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