clevotics-claude-bootstrap 1.0.1 → 1.0.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clevotics-claude-bootstrap",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "Claude Code skill that splits one Project Plan.md into PRD, ARCHITECTURE, DESIGN, a phased PLAN and a CLAUDE.md",
   "bin": {
     "clevotics-claude-bootstrap": "bin/cli.js"

package/project-bootstrap/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: project-bootstrap
-description: Turn a single project plan markdown file (e.g. "Project Plan.md") into a structured doc set - PRD.md, ARCHITECTURE.md, DESIGN.md, PLAN.md split into small numbered phases with exit criteria - and finish by writing a short CLAUDE.md that routes to them. Use when a repo has only a plan file and the user asks to bootstrap, split, structure or set up the project docs, or says "start this project from the plan".
+description: Turn a single project plan markdown file (e.g. "Project Plan.md") into a structured doc set - PRD.md, ARCHITECTURE.md, DESIGN.md, PLAN.md split into small numbered phases with exit criteria - and finish by writing a short CLAUDE.md that routes to them. Also restructures an existing project that already has a CLAUDE.md, code or docs, without losing any of it. Use when the user asks to bootstrap, split, structure, restructure or set up the project docs, or says "start this project from the plan".
 ---
 
 # Project Bootstrap
@@ -37,6 +37,18 @@ Add an extra doc only when the source has a large self-contained topic (an exter
 6. **Move the source plan** into `docs/` unchanged (`git mv` if tracked)
 7. Report: files created, phase count, decisions you made on the user's behalf, open questions left
 
+## Existing project mode
+
+Use this mode instead of steps 1 to 6 when the repo already has a `CLAUDE.md`, any of the target docs, or real code. The rule: restructure, never lose anything
+
+1. **Inventory first.** Read the existing `CLAUDE.md`, every `.md` under the root and `docs/`, the package / build files, and `git log --oneline -30`. Note what is already built
+2. **Show the mapping before writing.** Tell the user which existing section goes to which new doc, which files get created, and which get rewritten. Wait for a go-ahead, since this rewrites their instructions
+3. **Back up before rewriting.** Copy the current `CLAUDE.md` to `docs/CLAUDE.md.bak` (and any doc you will restructure, same pattern). The user deletes the backups once happy
+4. **Keep every rule.** Each rule, command and convention in the old `CLAUDE.md` either stays in the new `CLAUDE.md` or moves to the doc that owns it with a link back. Product and architecture explanations move out; hard rules, commands and routing stay
+5. **Keep existing docs that already fit.** If a doc already covers one bucket (e.g. an `API.md` that is the architecture), keep its name and route to it from `CLAUDE.md` instead of creating a duplicate
+6. **Plan from where the code is, not from zero.** Work already in the code and git history becomes DONE phases at the top of `PLAN.md`, each with a short Result line ("existing before bootstrap"). Remaining work from the plan or the old docs becomes TODO phases following the phase rules below
+7. **Verify nothing was dropped.** Before reporting, list each heading of the old `CLAUDE.md` and where its content now lives. Any heading without a home is a bug - fix it before reporting
+
 ## Phase rules (PLAN.md)
 
 A phase is the unit Claude finishes in one sitting, end to end