pi-skill-playbook 1.0.0 → 1.1.0

package/README.md

@@ -117,15 +117,26 @@ PLAYBOOK_OUTCOME: ready-for-prd
 | `suggest` | Marker only suggests `/playbook:done` or `/playbook:choose` |
 | `off` | No prompt injection or completion detection |
 
+## Sample playbooks
+
+| Playbook | File | When to use |
+|---|---|---|
+| Feature Development | `feature-development.yml` | Generic product work with standard `to-prd` / `to-issues` skills. Good default for non-OSS projects. |
+| Pi OSS New Extension Delivery | `pi-oss-new.yml` | Full Pi OSS lane from idea through PR verify and release post. Uses `-for-oss` skills and vault maintenance skills. |
+| Pi OSS Bootstrap Only | `pi-oss-bootstrap-only.yml` | Repo + vault bootstrap, then PRD and issue slicing only. Stops before implementation. |
+| OSS Maintenance Onboarding | `oss-maintenance-onboard.yml` | Add a new OSS target to the Multica maintenance operating model. |
+
+Copy one or more files from `samples/` into `.pi/playbooks/` in the target project. See [`docs/examples.md`](docs/examples.md) for copy-and-start steps.
+
 ## Package contents
 
 ```
 pi-skill-playbook/
 ├── extensions/     Pi extension entry point
 ├── src/            Domain logic: validation, state, rendering, auto-advance
-├── samples/        Example playbooks (feature-development.yml)
+├── samples/        Example playbooks (generic + Pi OSS lane)
 ├── tests/          Node.js test suite
-├── docs/adr/       Architecture decision records
+├── docs/           Examples and architecture decision records
 ├── LICENSE         MIT
 └── README.md
 ```
@@ -155,7 +166,7 @@ steps:
         to: complete        # "complete" ends the run
 ```
 
-See [`samples/feature-development.yml`](samples/feature-development.yml) for a full example.
+See [`samples/feature-development.yml`](samples/feature-development.yml) for a generic example and [`samples/pi-oss-new.yml`](samples/pi-oss-new.yml) for the Pi OSS delivery lane.
 
 ## Development
 
@@ -182,13 +193,14 @@ Manual dispatch is also available from the Actions tab.
 - Run state is local-only (`.pi/playbook-runs/`). No data leaves the machine.
 - The extension does **not** inject system prompts for skill execution. It only adds a short playbook prompt describing the current step, valid outcomes, and expected marker format.
 - No automatic file edits — the extension warns with a `.gitignore` snippet instead of modifying files.
-- Report vulnerabilities via [GitHub Security Advisories](https://github.com/eiei114/pi-skill-playbook/security/advisories/new).
+- For vulnerability reporting, see [`SECURITY.md`](SECURITY.md).
 
 ## Links
 
 - [npm package](https://www.npmjs.com/package/pi-skill-playbook)
 - [GitHub repository](https://github.com/eiei114/pi-skill-playbook)
 - [Pi coding agent](https://github.com/earendil-works/pi-coding-agent)
+- [Roadmap](ROADMAP.md)
 - [Architecture decisions](docs/adr/)
 
 ## License

package/docs/examples.md

@@ -1,11 +1,45 @@
 # Examples
 
-## Selection-first TUI flow
+## Copy a sample into your project
 
-Copy or create YAML playbooks in the target project under `.pi/playbooks/`, then use argument-free commands from the Pi TUI:
+Package samples ship under `samples/`. Copy the playbook that matches your lane into the target project's `.pi/playbooks/` folder:
+
+```bash
+mkdir -p .pi/playbooks
+
+# Generic feature development
+cp node_modules/pi-skill-playbook/samples/feature-development.yml .pi/playbooks/
+
+# Pi OSS delivery lane (idea -> PRD -> issues -> TDD -> review -> PR verify -> release post)
+cp node_modules/pi-skill-playbook/samples/pi-oss-new.yml .pi/playbooks/
+
+# Pi OSS bootstrap only (repo + vault setup -> PRD -> issues)
+cp node_modules/pi-skill-playbook/samples/pi-oss-bootstrap-only.yml .pi/playbooks/
+
+# Multica OSS maintenance onboarding
+cp node_modules/pi-skill-playbook/samples/oss-maintenance-onboard.yml .pi/playbooks/
+```
+
+Add run state to the target repo's `.gitignore`:
+
+```gitignore
+.pi/playbook-runs/
+```
+
+## Start a run
+
+From the Pi TUI, list playbooks and start one with the selection UI:
 
 ```text
+/playbook:list
 /playbook:start
+```
+
+When multiple playbooks exist, Pi shows a selector with validation status for each file. The run id is generated automatically.
+
+## Drive the workflow
+
+```text
 /skill:grill-with-docs <feature idea>
 /playbook:done
 /playbook:choose
@@ -16,3 +50,5 @@ Copy or create YAML playbooks in the target project under `.pi/playbooks/`, then
 - `/playbook:resume` opens an active-run selector.
 - `/playbook:choose` opens a selector for the current step's valid outcomes.
 - `/playbook:cancel` selects an active run when needed and asks for confirmation before marking it cancelled.
+
+For Pi OSS samples, run the skill named in the widget's command hint at each step. Single-outcome steps can auto-advance when the assistant emits a visible `PLAYBOOK_OUTCOME:` marker.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-skill-playbook",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "type": "module",
   "description": "Pi extension for passive, human-mediated Agent Skill playbooks.",
   "keywords": ["pi-package", "pi-extension", "agent-skills", "playbook"],

package/samples/oss-maintenance-onboard.yml

@@ -0,0 +1,22 @@
+version: 1
+id: oss-maintenance-onboard
+name: OSS Maintenance Onboarding
+entry: onboard
+autoAdvance: auto
+
+skills:
+  oss-maintenance-onboarding:
+    role: entry
+
+steps:
+  onboard:
+    primarySkill: oss-maintenance-onboarding
+    commandHint: "/skill:oss-maintenance-onboarding add this OSS target to Multica maintenance"
+    doneWhen:
+      - Target is registered in the vault maintenance control surface.
+      - Live Multica project is created or linked when requested.
+      - Controllers and Autopilot tracking are configured conservatively.
+      - Pilot issue verification notes are captured for the first maintenance slice.
+    transitions:
+      - outcome: complete
+        to: complete

package/samples/pi-oss-bootstrap-only.yml

@@ -0,0 +1,43 @@
+version: 1
+id: pi-oss-bootstrap-only
+name: Pi OSS Bootstrap Only
+entry: bootstrap
+autoAdvance: auto
+
+skills:
+  pi-oss-bootstrap:
+    role: entry
+  to-prd-for-oss:
+    role: internal
+  to-issues-for-oss:
+    role: internal
+
+steps:
+  bootstrap:
+    primarySkill: pi-oss-bootstrap
+    commandHint: "/skill:pi-oss-bootstrap bootstrap a new Pi extension OSS project"
+    doneWhen:
+      - OSS repo exists under Projects/OSS/.
+      - Vault project folder exists under 4_Project/OSS/<project_key>/.
+    transitions:
+      - outcome: ready-for-prd
+        to: prd
+
+  prd:
+    primarySkill: to-prd-for-oss
+    commandHint: "/skill:to-prd-for-oss create PRD in 4_Project/<project>/Docs/"
+    doneWhen:
+      - PRD exists under the target OSS project Docs folder.
+    transitions:
+      - outcome: ready-for-issues
+        to: issues
+
+  issues:
+    primarySkill: to-issues-for-oss
+    commandHint: "/skill:to-issues-for-oss break PRD into tracer-bullet issues"
+    doneWhen:
+      - Issue files exist under 4_Project/<project>/Issues/.
+      - Issues are independently grabbable.
+    transitions:
+      - outcome: complete
+        to: complete

package/samples/pi-oss-new.yml

@@ -0,0 +1,91 @@
+version: 1
+id: pi-oss-new
+name: Pi OSS New Extension Delivery
+entry: grill
+autoAdvance: auto
+
+skills:
+  grill-with-docs:
+    role: entry
+  to-prd-for-oss:
+    role: internal
+  to-issues-for-oss:
+    role: internal
+  tdd:
+    role: internal
+  review:
+    role: internal
+  pi-extension-pr-verify:
+    role: internal
+  x-release-post:
+    role: internal
+
+steps:
+  grill:
+    primarySkill: grill-with-docs
+    commandHint: "/skill:grill-with-docs <Pi OSS extension idea>"
+    doneWhen:
+      - Problem boundary is clear for the new Pi OSS project.
+      - Key terminology and repo layout are resolved.
+    transitions:
+      - outcome: ready-for-prd
+        to: prd
+
+  prd:
+    primarySkill: to-prd-for-oss
+    commandHint: "/skill:to-prd-for-oss create PRD in 4_Project/<project>/Docs/"
+    doneWhen:
+      - PRD exists under the target OSS project Docs folder.
+    transitions:
+      - outcome: ready-for-issues
+        to: issues
+
+  issues:
+    primarySkill: to-issues-for-oss
+    commandHint: "/skill:to-issues-for-oss break PRD into tracer-bullet issues"
+    doneWhen:
+      - Issue files exist under 4_Project/<project>/Issues/.
+      - Issues are independently grabbable.
+    transitions:
+      - outcome: ready-for-implementation
+        to: implement
+
+  implement:
+    primarySkill: tdd
+    commandHint: "/skill:tdd implement the next OSS issue"
+    doneWhen:
+      - Tests pass.
+      - Implementation is complete for the current slice.
+    transitions:
+      - outcome: ready-for-review
+        to: review
+
+  review:
+    primarySkill: review
+    commandHint: "/skill:review review this branch against the plan"
+    doneWhen:
+      - Standards and spec review results are known.
+    transitions:
+      - outcome: pass
+        to: pr-verify
+      - outcome: fail
+        to: implement
+
+  pr-verify:
+    primarySkill: pi-extension-pr-verify
+    commandHint: "/skill:pi-extension-pr-verify verify the PR locally"
+    doneWhen:
+      - PR worktree is set up and automated checks pass.
+      - Manual Pi TUI verification checklist is complete.
+    transitions:
+      - outcome: ready-for-release
+        to: release-post
+
+  release-post:
+    primarySkill: x-release-post
+    commandHint: "/skill:x-release-post draft X release announcement"
+    doneWhen:
+      - English and Japanese release post drafts are saved.
+    transitions:
+      - outcome: complete
+        to: complete