@schalkneethling/toolkit 0.3.0 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/commands/rpm-advance.md +13 -0
- package/commands/rpm-checkpoint.md +13 -0
- package/commands/rpm-feedback.md +15 -0
- package/commands/rpm-handoff.md +14 -0
- package/commands/rpm-review.md +13 -0
- package/commands/rpm-start.md +13 -0
- package/package.json +2 -1
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
# /rpm:advance
|
|
2
|
+
|
|
3
|
+
Use the Refined Plan Mode skill to continue the loop from the current state.
|
|
4
|
+
|
|
5
|
+
Steps:
|
|
6
|
+
|
|
7
|
+
1. Inspect `.plan-review/.current-version`, `.plan-review/approved-plan.md`, available plan files, and available feedback files.
|
|
8
|
+
2. If an approved plan exists, execute that plan.
|
|
9
|
+
3. If feedback exists for the current plan version, incorporate it into the next plan version.
|
|
10
|
+
4. If there is a current plan but no feedback or approval, remind the user that the plan is awaiting review.
|
|
11
|
+
5. If no plan exists, start with `/rpm:start` behavior.
|
|
12
|
+
|
|
13
|
+
Keep the response focused on the next state transition.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
# /rpm:checkpoint
|
|
2
|
+
|
|
3
|
+
Use the Refined Plan Mode skill to summarize the current review-loop state.
|
|
4
|
+
|
|
5
|
+
Report:
|
|
6
|
+
|
|
7
|
+
- Current plan version from `.plan-review/.current-version`, if present.
|
|
8
|
+
- Latest plan file path.
|
|
9
|
+
- Whether feedback exists for the current version.
|
|
10
|
+
- Whether `.plan-review/approved-plan.md` exists.
|
|
11
|
+
- The recommended next action.
|
|
12
|
+
|
|
13
|
+
Do not modify files unless the user also asks you to advance or revise the plan.
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
# /rpm:feedback
|
|
2
|
+
|
|
3
|
+
Use the Refined Plan Mode skill to incorporate submitted feedback into the next plan version.
|
|
4
|
+
|
|
5
|
+
Steps:
|
|
6
|
+
|
|
7
|
+
1. Read `.plan-review/.current-version` to find the current version.
|
|
8
|
+
2. Read `.plan-review/feedback/plan-vN-feedback.json` for that version.
|
|
9
|
+
3. Read `.plan-review/plans/plan-vN.md`.
|
|
10
|
+
4. Address every feedback item in a revised plan, adding a "Feedback Addressed" section that maps comments to changes made.
|
|
11
|
+
5. Write the revision to `.plan-review/plans/plan-vN+1.md`.
|
|
12
|
+
6. Update `.plan-review/.current-version` to the new version.
|
|
13
|
+
7. Reply with a short note naming the feedback file read and the new plan file written.
|
|
14
|
+
|
|
15
|
+
If the feedback file is missing, report the exact path expected and stop.
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
# /rpm:handoff
|
|
2
|
+
|
|
3
|
+
Use the Refined Plan Mode skill to prepare a compact continuation summary for another agent or a future session.
|
|
4
|
+
|
|
5
|
+
Include:
|
|
6
|
+
|
|
7
|
+
- Goal.
|
|
8
|
+
- Current plan version and file path.
|
|
9
|
+
- Feedback status.
|
|
10
|
+
- Approval status.
|
|
11
|
+
- Important assumptions or unresolved decisions.
|
|
12
|
+
- Recommended next command or action.
|
|
13
|
+
|
|
14
|
+
Prefer reading the current plan and feedback files directly instead of relying on chat history.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
# /rpm:review
|
|
2
|
+
|
|
3
|
+
Use the Refined Plan Mode skill to audit the latest plan before the user reviews it.
|
|
4
|
+
|
|
5
|
+
Steps:
|
|
6
|
+
|
|
7
|
+
1. Read the current plan version.
|
|
8
|
+
2. Review the plan for missing context, vague steps, untested assumptions, risky sequencing, and weak validation.
|
|
9
|
+
3. If improvements are needed, write a revised next version and update `.plan-review/.current-version`.
|
|
10
|
+
4. If the plan is already review-ready, leave files unchanged.
|
|
11
|
+
5. Reply with either the new plan version written or a short explanation that the current plan is ready for review.
|
|
12
|
+
|
|
13
|
+
This command reviews plan quality. It does not implement the plan.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
# /rpm:start
|
|
2
|
+
|
|
3
|
+
Use the Refined Plan Mode skill to start a plan review loop for the user's current task.
|
|
4
|
+
|
|
5
|
+
Steps:
|
|
6
|
+
|
|
7
|
+
1. Inspect the repository enough to understand the task and relevant constraints.
|
|
8
|
+
2. Ask only blocking clarification questions. If reasonable assumptions are available, state them in the plan instead of stopping.
|
|
9
|
+
3. Create `.plan-review/plans/plan-v1.md` with the complete plan.
|
|
10
|
+
4. Create or update `.plan-review/.current-version` with `v1`.
|
|
11
|
+
5. Reply with a concise summary and tell the user the plan is ready for review in Refined Plan Mode.
|
|
12
|
+
|
|
13
|
+
Do not implement the plan yet unless the user explicitly asks you to proceed without review.
|
package/package.json
CHANGED
|
@@ -1,12 +1,13 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@schalkneethling/toolkit",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.4.0",
|
|
4
4
|
"description": "CLI for managing Claude Code hooks and skills across projects.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"bin": {
|
|
7
7
|
"toolkit": "./dist/index.mjs"
|
|
8
8
|
},
|
|
9
9
|
"files": [
|
|
10
|
+
"commands",
|
|
10
11
|
"dist",
|
|
11
12
|
"hooks",
|
|
12
13
|
"!**/*.ts",
|