@theglitchking/persistent-planning 3.6.1 → 3.6.2
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.
|
@@ -6,13 +6,13 @@
|
|
|
6
6
|
},
|
|
7
7
|
"metadata": {
|
|
8
8
|
"description": "Official marketplace for persistent-planning - Persistent markdown-based planning for Claude Code. Context engineering pattern with task directories, progress tracking, and working memory that persists across sessions.",
|
|
9
|
-
"version": "3.6.
|
|
9
|
+
"version": "3.6.2"
|
|
10
10
|
},
|
|
11
11
|
"plugins": [
|
|
12
12
|
{
|
|
13
13
|
"name": "persistent-planning",
|
|
14
14
|
"description": "Persistent markdown-based planning for Claude Code. Uses on-disk markdown files as working memory for planning, progress tracking, and knowledge storage. Plans persist across sessions and support multiple concurrent tasks.",
|
|
15
|
-
"version": "3.6.
|
|
15
|
+
"version": "3.6.2",
|
|
16
16
|
"author": {
|
|
17
17
|
"name": "TheGlitchKing"
|
|
18
18
|
},
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "persistent-planning",
|
|
3
|
-
"version": "3.6.
|
|
3
|
+
"version": "3.6.2",
|
|
4
4
|
"description": "Persistent markdown-based planning with task directories, progress tracking, and context engineering for multi-step Claude Code workflows",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "TheGlitchKing"
|
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,16 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
|
4
4
|
|
|
5
|
+
## [3.6.2] - 2026-11-09
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
|
|
9
|
+
- **A plan's branch is cut from `main`.** Step 2 of the git-workflow section read
|
|
10
|
+
"Cut a new branch" and only implied `main` through step 1's sync. It now reads
|
|
11
|
+
"Cut a branch from `main`", with the base in the command
|
|
12
|
+
(`git checkout -b <type>/<plan-slug> main`). The section is appended once, so a
|
|
13
|
+
repo that already has it keeps the old wording until edited.
|
|
14
|
+
|
|
5
15
|
## [3.6.1] - 2026-10-23
|
|
6
16
|
|
|
7
17
|
### Fixed — archived plans stayed tracked in git (#26)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@theglitchking/persistent-planning",
|
|
3
|
-
"version": "3.6.
|
|
3
|
+
"version": "3.6.2",
|
|
4
4
|
"description": "Persistent markdown-based planning with task directories, progress tracking, and context engineering for multi-step Claude Code workflows",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
These are hard requirements on every plan under `.planning/`:
|
|
5
5
|
|
|
6
6
|
1. **Sync `main` first.** `git checkout main && git fetch origin main && git merge --ff-only origin/main`.
|
|
7
|
-
2. **Cut a
|
|
7
|
+
2. **Cut a branch from `main`** for the plan before changing anything: `git checkout -b <type>/<plan-slug> main`.
|
|
8
8
|
3. **Implement the plan through to completion**: every phase, including the mandatory cleanup,
|
|
9
9
|
validation and documentation steps, until `/plan-status` reads COMPLETE.
|
|
10
10
|
4. **Commit at the end of each phase** (sm: each item under `## Phases`; lg: each task).
|