@pdlc-os/pdlc 0.1.0 → 0.1.1

package/.claude/commands/brainstorm.md

@@ -345,9 +345,21 @@ Append to Phase History:
 > - PRD: `docs/pdlc/prds/PRD_[feature-name]_[YYYY-MM-DD].md`
 > - Design: `docs/pdlc/design/[feature-name]/`
 > - Plan: `docs/pdlc/prds/plans/plan_[feature-name]_[YYYY-MM-DD].md`
-> - Beads tasks created: [N]
+> - Beads tasks created: [N]"
+
+Then immediately ask:
+
+> "Would you like to move to Construction and start building `[feature-name]` now?
 >
-> Run `/pdlc build` to begin Construction."
+> - Say **yes** to begin immediately
+> - Or type `/pdlc build` at any time to start manually"
+
+**If the user responds with "yes", "y", "sure", "go ahead", or any clear affirmative**:
+→ Immediately begin executing the `/pdlc build` flow without waiting for the user to type the command.
+
+**If the user responds with "no", "not yet", "later", or any deferral**:
+→ Acknowledge and stop:
+> "No problem. When you're ready, run `/pdlc build` to begin Construction."
 
 ---
 

package/.claude/commands/build.md

@@ -139,7 +139,7 @@ If the user chose **B**: proceed as a single focused sub-agent.
 
 ### Step 9 — TDD: Build the task
 
-Follow the TDD protocol from `skills/tdd.md` exactly. The key steps:
+Follow the TDD protocol from `skills/tdd/SKILL.md` exactly. The key steps:
 
 **9a. Read the task context:**
 - Run `bd show [task-id]` to get the full task with acceptance criteria
@@ -214,7 +214,7 @@ Once `bd ready` is empty (all tasks complete):
 
 ### Step 12 — Run the review protocol
 
-Follow `skills/review.md` exactly.
+Follow `skills/review/SKILL.md` exactly.
 
 **Context to load:**
 - The full list of tasks completed (from Phase History in STATE.md)
@@ -276,7 +276,7 @@ Update `docs/pdlc/memory/STATE.md`:
 
 ### Step 15 — Run each test layer
 
-Run the test layers per `skills/test.md` (when available). Check CONSTITUTION.md §7 for which gates are required.
+Run the test layers per `skills/test/SKILL.md` (when available). Check CONSTITUTION.md §7 for which gates are required.
 
 Run each layer in this order:
 
@@ -367,9 +367,21 @@ Append to Phase History:
 >
 > - All [N] tasks done in Beads
 > - Review approved: `docs/pdlc/reviews/REVIEW_[feature-name]_[YYYY-MM-DD].md`
-> - Episode draft: `docs/pdlc/memory/episodes/[NNN]_[feature-name]_[YYYY-MM-DD].md`
+> - Episode draft ready: `docs/pdlc/memory/episodes/[NNN]_[feature-name]_[YYYY-MM-DD].md`"
+
+Then immediately ask:
+
+> "Would you like to move to Operation and ship `[feature-name]` now?
 >
-> Review the episode draft, then run `/pdlc ship` to deploy."
+> - Say **yes** to begin immediately
+> - Or type `/pdlc ship` at any time to start manually"
+
+**If the user responds with "yes", "y", "sure", "go ahead", or any clear affirmative**:
+→ Immediately begin executing the `/pdlc ship` flow without waiting for the user to type the command.
+
+**If the user responds with "no", "not yet", "later", or any deferral**:
+→ Acknowledge and stop:
+> "No problem. The episode draft is ready for your review. Run `/pdlc ship` when you're ready to deploy."
 
 ---
 

package/.claude/commands/init.md

@@ -56,7 +56,7 @@ For a brownfield project, tell the user:
 > - **Yes** — I'll analyse the codebase and pre-populate your memory files. You'll review and approve my findings before anything is written.
 > - **No** — We'll continue with the standard Socratic questions and blank templates."
 
-**If the user says yes:** run the full `skills/repo-scan.md` protocol now. The repo scan will:
+**If the user says yes:** run the full `skills/repo-scan/SKILL.md` protocol now. The repo scan will:
 1. Map the repo structure and read key files
 2. Synthesise findings into a structured summary
 3. Present the summary for your review and approval
@@ -365,6 +365,27 @@ Replace counts (e.g. `[N] decisions`) with actual numbers from the scan.
 
 ---
 
+## Step 10 — Prompt for next phase
+
+After printing the initialization summary, ask the user:
+
+> "Would you like to start Inception now and brainstorm your first feature?
+>
+> - Say **yes** (or provide a feature name) to begin immediately
+> - Or type `/pdlc brainstorm <feature-name>` at any time to start manually"
+
+**If the user responds with "yes", "y", "sure", "go ahead", or any clear affirmative** (with or without a feature name):
+→ Ask "What feature would you like to start with?" if no feature name was given, then immediately begin executing the `/pdlc brainstorm` flow.
+
+**If the user provides a feature name directly** (e.g. "yes, user-auth" or just "user-auth"):
+→ Immediately begin executing `/pdlc brainstorm user-auth` without any further prompting.
+
+**If the user responds with "no", "not yet", "later", or any deferral**:
+→ Acknowledge and stop:
+> "No problem. When you're ready, run `/pdlc brainstorm <feature-name>` to start Inception."
+
+---
+
 ## Safety notes
 
 - This command is safe to run only once. If `docs/pdlc/memory/CONSTITUTION.md` already exists, warn the user: "PDLC appears to already be initialized (docs/pdlc/memory/CONSTITUTION.md exists). Re-running init will overwrite the memory files. Are you sure? (yes/no)" — wait for confirmation before proceeding.

package/CLAUDE.md

@@ -1,6 +1,6 @@
 # PDLC — Product Development Lifecycle
 
-You are operating within the PDLC (Product Development Lifecycle) framework, a structured Claude Code plugin designed for small startup teams (2–5 engineers). PDLC guides every feature from raw idea through shipping and retrospective across four phases: Initialization, Inception, Construction, and Operation. The framework combines methodology discipline (TDD, systematic debugging, subagent reviews), specialist agent roles, context-rot prevention, spec-driven execution, and file-based persistent memory. Every session begins by reading `docs/pdlc/memory/STATE.md` to determine where work left off, then resumes automatically from the last checkpoint. All rules, standards, and overrides live in `docs/pdlc/memory/CONSTITUTION.md` — the Constitution always wins.
+You are operating within the PDLC (Product Development Lifecycle) framework, a structured Claude Code plugin designed for small startup-style teams (2–5 engineers). PDLC guides every feature from raw idea through shipping and retrospective across four phases: Initialization, Inception, Construction, and Operation. The framework combines methodology discipline (TDD, systematic debugging, subagent reviews), specialist agent roles, context-rot prevention, spec-driven execution, and file-based persistent memory. Every session begins by reading `docs/pdlc/memory/STATE.md` to determine where work left off, then resumes automatically from the last checkpoint. All rules, standards, and overrides live in `docs/pdlc/memory/CONSTITUTION.md` — the Constitution always wins.
 
 ---
 

package/README.md

@@ -1,6 +1,6 @@
 # PDLC — Product Development Lifecycle
 
-A Claude Code plugin that guides small startup teams (2–5 engineers) through the full arc of feature development — from raw idea to shipped, production feature — using structured phases, a named specialist agent team, persistent memory, and safety guardrails.
+A Claude Code plugin that guides small startup-style teams (2–5 engineers) through the full arc of feature development — from raw idea to shipped, production feature — using structured phases, a named specialist agent team, persistent memory, and safety guardrails.
 
 PDLC combines the best of three Claude Code workflows:
 - **[obra/superpowers](https://github.com/obra/superpowers)** — TDD discipline, systematic debugging, visual brainstorming companion
@@ -35,14 +35,36 @@ PDLC combines the best of three Claude Code workflows:
 npx @pdlc-os/pdlc install
 ```
 
-### Option B — global install
+### Option B — global npm install
 
 ```bash
 npm install -g @pdlc-os/pdlc
 pdlc install
 ```
 
-Both commands register PDLC's hooks and status bar in `~/.claude/settings.json`. Start a new Claude Code session to activate.
+### Option C — directly from GitHub (always latest)
+
+```bash
+npm install -g pdlc-os/pdlc
+pdlc install
+```
+
+Pin to a specific release tag:
+
+```bash
+npm install -g pdlc-os/pdlc#v0.1.0
+pdlc install
+```
+
+### Option D — clone and install
+
+```bash
+git clone https://github.com/pdlc-os/pdlc.git
+cd pdlc
+node bin/pdlc.js install
+```
+
+All options register PDLC's hooks and status bar in `~/.claude/settings.json`. Start a new Claude Code session to activate.
 
 ### Verify installation
 
@@ -59,7 +81,11 @@ npx @pdlc-os/pdlc uninstall
 ### Keep up to date
 
 ```bash
+# From npm
 npx @pdlc-os/pdlc@latest install
+
+# From GitHub (latest main)
+npm install -g pdlc-os/pdlc && pdlc install
 ```
 
 Re-running `install` is idempotent — it strips old hook paths and re-registers with the current version.
@@ -233,6 +259,8 @@ All inferred content is clearly marked `(inferred — please verify)` so the tea
 
 Four sub-phases, each with a human approval gate:
 
+At any point during Socratic questioning, type **`skip`** to stop questions and proceed immediately with the information collected so far.
+
 | Sub-phase | Output |
 |-----------|--------|
 | **Discover** | Socratic Q&A + external context (web, Figma, Notion, OneDrive) + visual companion |
@@ -415,6 +443,13 @@ The server shuts down automatically when Inception ends or after 30 minutes of i
 
 ## pdlc-os Marketplace
 
+| Resource | URL |
+|----------|-----|
+| GitHub org | https://github.com/pdlc-os |
+| Core package | https://www.npmjs.com/package/@pdlc-os/pdlc |
+| Registry index | https://github.com/pdlc-os/registry |
+| Contribution guide | https://github.com/pdlc-os/registry/blob/main/CONTRIBUTING.md |
+
 The `pdlc-os` GitHub organisation hosts community-contributed extensions that extend PDLC's built-in capabilities. All packages are published under the `@pdlc-os/` npm scope.
 
 **What the marketplace hosts:**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pdlc-os/pdlc",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Product Development Lifecycle — a Claude Code plugin for small startup teams",
   "keywords": [
     "claude-code",