@sienklogic/plan-build-run 2.38.1 → 2.40.0

package/CHANGELOG.md

@@ -5,6 +5,32 @@ All notable changes to Plan-Build-Run will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.40.0](https://github.com/SienkLogic/plan-build-run/compare/plan-build-run-v2.39.0...plan-build-run-v2.40.0) (2026-02-27)
+
+
+### Features
+
+* **milestone:** add push/publish step after milestone complete ([dc26503](https://github.com/SienkLogic/plan-build-run/commit/dc26503975691480e805893e1fb400cf41b01226))
+
+
+### Bug Fixes
+
+* **tools:** find per-plan SUMMARY-{id}.md files in milestone-learnings aggregation ([2ecda9f](https://github.com/SienkLogic/plan-build-run/commit/2ecda9ff555d3787e2bea92f339d7abb9afc5e04))
+
+## [2.39.0](https://github.com/SienkLogic/plan-build-run/compare/plan-build-run-v2.38.1...plan-build-run-v2.39.0) (2026-02-27)
+
+
+### Features
+
+* **45-01:** add learnings subcommands to pbr-tools.js dispatcher ([a2c9b98](https://github.com/SienkLogic/plan-build-run/commit/a2c9b98a60291611b85b086a4c274fa4ee82477b))
+* **45-01:** add lib/learnings.js with schema, storage, ingest, and query ([feb6bf6](https://github.com/SienkLogic/plan-build-run/commit/feb6bf6b2b1adcedc71d0558804a722be60aac77))
+* **45-03:** add deferral notifications to progress-tracker and aggregation step to milestone skill ([ac89d05](https://github.com/SienkLogic/plan-build-run/commit/ac89d05323d8b8468718bfad52181cf72b635ce6))
+* **45-03:** GREEN - milestone-learnings.js aggregation script ([68fa377](https://github.com/SienkLogic/plan-build-run/commit/68fa3778937825ad09b1b38cb5b626abf68dffc1))
+* **45-04:** add learnings injection to begin/SKILL.md researcher spawn step ([ebe3970](https://github.com/SienkLogic/plan-build-run/commit/ebe39702e4f04a2576b6e0ad6b7edb6e93672a4c))
+* **45-04:** add learnings injection to explore/SKILL.md and plan skill planner spawn ([53644cf](https://github.com/SienkLogic/plan-build-run/commit/53644cf9601ff47341ebde40c712e99d54f34ebb))
+* **45-05:** sync learnings injection and aggregation to cursor-pbr and copilot-pbr ([eef6a0c](https://github.com/SienkLogic/plan-build-run/commit/eef6a0caa5f19629d08d0cce878b51a7823b9424))
+* **quick-019:** add ecosystem integration — PR creation, CI gate, issue sync, smoke test ([c57e44e](https://github.com/SienkLogic/plan-build-run/commit/c57e44ede58d167cd69ffe5403cc20645c537635))
+
 ## [2.38.1](https://github.com/SienkLogic/plan-build-run/compare/plan-build-run-v2.38.0...plan-build-run-v2.38.1) (2026-02-27)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sienklogic/plan-build-run",
-  "version": "2.38.1",
+  "version": "2.40.0",
   "description": "Plan it, Build it, Run it — structured development workflow for Claude Code",
   "keywords": [
     "claude-code",

package/plugins/copilot-pbr/agents/executor.agent.md

@@ -114,6 +114,19 @@ One task = one commit. Exception: TDD tasks get 3 commits (RED, GREEN, REFACTOR)
 
 Stage only files listed in the task's `<files>`. If git commit fails with lock error, retry up to 3 times with 2s delay.
 
+### Issue Auto-Close
+
+When the plan frontmatter contains a non-empty `closes_issues` array, append issue-closing syntax to the **final** commit body for the plan:
+
+```
+git commit -m "feat(01-02): implement user auth
+
+Closes #42
+Closes #57"
+```
+
+Only append to the LAST commit of the plan — intermediate commits (RED/GREEN in TDD, partial progress) should NOT include closing syntax.
+
 ---
 
 ## Deviation Rules

package/plugins/copilot-pbr/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "pbr",
   "displayName": "Plan-Build-Run",
-  "version": "2.38.1",
+  "version": "2.40.0",
   "description": "Plan-Build-Run — Structured development workflow for GitHub Copilot CLI. Solves context rot through disciplined agent delegation, structured planning, atomic execution, and goal-backward verification.",
   "author": {
     "name": "SienkLogic",

package/plugins/copilot-pbr/references/config-reference.md

@@ -156,11 +156,23 @@ Controls git integration and branching strategy.
 | `phase_branch_template` | string | `plan-build-run/phase-{phase}-{slug}` | Phase branch name pattern |
 | `milestone_branch_template` | string | `plan-build-run/{milestone}-{slug}` | Milestone branch name pattern |
 | `mode` | string | `enabled` | Git mode: `enabled` or `disabled` |
+| `auto_pr` | boolean | `false` | Create a GitHub PR after successful phase verification when branching is enabled |
 
 When `git.mode` is `disabled`, no git commands run at all -- no commits, branching, or hook validation. Useful for prototyping or non-git projects. See `references/git-integration.md` for full branching strategy details.
 
 ---
 
+## ci
+
+Controls CI integration for build gates.
+
+| Property | Type | Default | Description |
+|----------|------|---------|-------------|
+| `ci.gate_enabled` | boolean | `false` | Block wave advancement until CI passes |
+| `ci.wait_timeout_seconds` | number | `120` | Max seconds to wait for CI completion |
+
+---
+
 ## gates
 
 Confirmation gates that pause execution to ask the user before proceeding. Setting a gate to `false` makes that step automatic.
@@ -220,6 +232,16 @@ This value is overridden by the active depth profile if a `depth_profiles` entry
 
 ---
 
+## deployment
+
+Controls post-milestone deployment verification.
+
+| Property | Type | Default | Description |
+|----------|------|---------|-------------|
+| `deployment.smoke_test_command` | string | `""` | Bash command to run after milestone completion (e.g., `"curl -sf https://myapp.com/health"`) |
+
+---
+
 ## depth_profiles
 
 Override the built-in depth profile defaults. Each key (`quick`, `standard`, `comprehensive`) maps to an object of settings that take effect when that depth is active.

package/plugins/copilot-pbr/references/git-integration.md

@@ -175,6 +175,36 @@ Branch name templates are configured in `config.json`:
 - `git.phase_branch_template`: Default `plan-build-run/phase-{phase}-{slug}`
 - `git.milestone_branch_template`: Default `plan-build-run/{milestone}-{slug}`
 
+### PR Creation
+
+When `git.auto_pr: true` and `git.branching` is `phase` or `milestone`, the build skill creates a GitHub PR after verification passes:
+
+1. Push the phase branch to the remote
+2. Create a PR via `gh pr create` with structured title and body
+3. PR title follows the commit convention: `feat(phase-{N}): {phase slug}`
+4. PR body includes phase goal, key files changed, and must-have verification results
+
+When `git.auto_pr: false` (default), the build skill offers the user a choice after verification:
+- Create PR now
+- Skip PR creation
+- Push branch only (create PR later)
+
+PR creation requires `gh` CLI authenticated with repo write access.
+
+### CI Integration
+
+When `ci.gate_enabled: true`, the build skill checks GitHub Actions status after each wave completes:
+
+1. Run: `gh run list --branch $(git branch --show-current) --limit 1 --json status,conclusion,url`
+2. If `status == completed` and `conclusion == success`: proceed to next wave
+3. If `status == in_progress`: wait up to `ci.wait_timeout_seconds`, re-check
+4. If `conclusion != success` or timeout: surface warning with run URL and offer:
+   - **Wait**: continue polling
+   - **Continue anyway**: proceed despite CI failure (logged as deviation)
+   - **Abort**: stop the build
+
+CI gate requires `gh` CLI and GitHub Actions configured on the repository. The gate only activates when there are commits pushed to a remote branch (branching must be enabled).
+
 ### Git Mode
 
 The `git.mode` field controls whether git integration is active:

package/plugins/copilot-pbr/references/plan-format.md

@@ -47,6 +47,9 @@ consumes:
 requirement_ids:
   - "P02-G1"
   - "P02-G2"
+closes_issues:
+  - 42
+  - 57
 ---
 ```
 
@@ -72,6 +75,7 @@ requirement_ids:
 | `requirement_ids` | NO | array | Requirement IDs from REQUIREMENTS.md or ROADMAP.md goal IDs that this plan addresses. Enables bidirectional traceability between plans and requirements/goals. |
 | `dependency_fingerprints` | NO | object | Hashes of dependency phase SUMMARY.md files at plan-creation time. Used to detect stale plans. |
 | `data_contracts` | NO | array | Cross-boundary parameter mappings for calls where arguments originate from external boundaries. Format: `"param: source (context) [fallback]"` |
+| `closes_issues` | NO | number[] | GitHub issue numbers to close when this plan's final commit lands. Default: `[]` |
 
 ### Data Contracts
 

package/plugins/copilot-pbr/skills/begin/SKILL.md

@@ -212,6 +212,25 @@ Spawn parallel agents for research. Each researcher writes to `.planning/researc
 
 **CRITICAL: Create .planning/research/ directory NOW before spawning researchers. Do NOT skip this step.**
 
+**Learnings injection (opt-in):** Before spawning researchers, check if global learnings exist:
+
+```bash
+node {resolved_plugin_root}/scripts/pbr-tools.js learnings query --tags "stack,tech" 2>/dev/null
+```
+
+If the command succeeds AND returns a non-empty JSON array:
+
+- Write the results to a temp file:
+
+  ```bash
+  node {resolved_plugin_root}/scripts/pbr-tools.js learnings query --tags "stack,tech" > /tmp/pbr-learnings-$$.md
+  ```
+
+- Note the temp file path as `{learnings_temp_path}`
+- Add this file to the researcher's `files_to_read` block (see below)
+
+If no learnings exist or the command fails: skip injection silently.
+
 **For each research topic, invoke the @researcher agent:**
 
 Invoke `@researcher` with the research prompt constructed from the template.
@@ -231,9 +250,12 @@ Read `skills/begin/templates/researcher-prompt.md.tmpl` for the prompt structure
 <files_to_read>
 CRITICAL: Read these files BEFORE any other action:
 1. .planning/REQUIREMENTS.md — scoped requirements (if exists)
+{if learnings_temp_path exists}2. {learnings_temp_path} — cross-project learnings (tech stack patterns from past PBR projects){/if}
 </files_to_read>
 ```
 
+If `{learnings_temp_path}` was produced in the learnings injection step above, replace `{if...}{/if}` with the actual line. If no learnings were found, omit line 2 entirely.
+
 **Placeholders to fill:**
 - `{project name from questioning}` — project name gathered in Step 2
 - `{2-3 sentence description from questioning}` — project description from Step 2

package/plugins/copilot-pbr/skills/build/SKILL.md

@@ -614,6 +614,26 @@ Resume at: Task {N+1} (or re-execute checkpoint task with user's answer)
 Continue execution from the checkpoint. Skip completed tasks. Process the checkpoint resolution, then continue with remaining tasks. Write SUMMARY.md when done.
 ```
 
+#### 6e-ii. CI Gate (after wave completion, conditional)
+
+If `config.ci.gate_enabled` is `true` AND `config.git.branching` is not `none`:
+
+1. Push current commits: `git push`
+2. Wait 5 seconds for CI to trigger
+3. Check: `gh run list --branch $(git branch --show-current) --limit 1 --json status,conclusion,url`
+4. If in_progress: poll every 15 seconds up to `config.ci.wait_timeout_seconds`
+5. If failed/timed out: show warning box:
+
+   ```
+   ⚠ CI Status: {conclusion}
+   Run: {url}
+   Options: [Wait] [Continue anyway] [Abort]
+   ```
+
+6. Use AskUserQuestion to present options: Wait / Continue anyway / Abort
+7. If "Continue anyway": log deviation — `DEVIATION: CI gate bypassed for wave {N}`
+8. If "Abort": stop build, update STATE.md
+
 #### 6f. Update STATE.md
 
 After each wave completes (all plans in the wave are done, skipped, or aborted):
@@ -789,6 +809,31 @@ If `git.branching` is `phase`:
 - If "Yes, merge": complete the merge and delete the phase branch
 - If "No, keep" or "Other": leave the branch as-is and inform the user
 
+**8d-ii. PR Creation (when branching enabled):**
+
+If `config.git.branching` is `phase` or `milestone` AND phase verification passed:
+
+1. Push the phase branch: `git push -u origin {branch-name}`
+2. If `config.git.auto_pr` is `true`:
+   - Run: `gh pr create --title "feat({phase-scope}): {phase-slug}" --body "$(cat <<'EOF'
+## Phase {N}: {phase name}
+
+**Goal**: {phase goal from ROADMAP.md}
+
+### Key Files
+{key_files from SUMMARY.md, bulleted}
+
+### Verification
+{pass/fail status from VERIFICATION.md}
+
+---
+Generated by Plan-Build-Run
+EOF
+)"`
+3. If `config.git.auto_pr` is `false`:
+   - Use AskUserQuestion to ask: "Phase branch pushed. Create a PR?"
+   - Options: Yes (create PR as above) / No / Later (skip)
+
 **8e. Auto-advance / auto-continue (conditional):**
 
 **If `features.auto_advance` is `true` AND `mode` is `autonomous`:**

package/plugins/copilot-pbr/skills/explore/SKILL.md

@@ -115,6 +115,19 @@ When a knowledge gap emerges during the conversation — you're unsure about a l
 
 Display to the user: `◐ Spawning researcher...`
 
+**Learnings injection (opt-in):** Check for relevant tech stack learnings:
+
+```bash
+node {resolved_plugin_root}/scripts/pbr-tools.js learnings query --tags "stack,tech" 2>/dev/null
+```
+
+If non-empty JSON array returned:
+
+- Write to temp file: `node {resolved_plugin_root}/scripts/pbr-tools.js learnings query --tags "stack,tech" > /tmp/pbr-learnings-$$.md`
+- Note path as `{learnings_temp_path}`; add as item 3 in the researcher's `files_to_read` block below
+
+If no learnings or command fails: omit the extra files_to_read entry.
+
 ```
 Task({
   subagent_type: "pbr:researcher",
@@ -122,6 +135,7 @@ Task({
     CRITICAL: Read these files BEFORE any other action:
     1. .planning/CONTEXT.md — locked decisions and constraints (if exists)
     2. .planning/STATE.md — current project state (if exists)
+    {if learnings_temp_path exists}3. {learnings_temp_path} — cross-project learnings (tech stack patterns from past PBR projects){/if}
   </files_to_read>
   <research_assignment>
     Topic: {specific research question}
@@ -135,6 +149,9 @@ Task({
 })
 ```
 
+If `{learnings_temp_path}` was produced above, replace `{if...}{/if}` with the actual line. If no learnings were found, omit item 3 entirely.
+```
+
 After the researcher completes, check for completion markers in the Task() output:
 
 - If `## RESEARCH COMPLETE` is present: proceed normally

package/plugins/copilot-pbr/skills/milestone/SKILL.md

@@ -412,6 +412,28 @@ Archive a completed milestone and prepare for the next one.
      - Key deliverables: {summary from Step 4}
      ```
 
+7d. **Aggregate learnings from milestone phases:**
+
+**CRITICAL: Run learnings aggregation NOW. Do NOT skip this step.**
+
+```bash
+node ${PLUGIN_ROOT}/scripts/milestone-learnings.js .planning/milestones/{version} --project {project-name-from-STATE.md}
+```
+
+- If the script outputs an error, log it but do NOT abort milestone completion — learnings aggregation is advisory.
+- Display the aggregation summary line to the user (e.g., "Learnings aggregated: 12 new, 3 updated, 0 errors").
+- After aggregation, check for triggered deferral thresholds:
+
+```bash
+node ${PLUGIN_ROOT}/scripts/pbr-tools.js learnings check-thresholds
+```
+
+If any thresholds are triggered, display each as a notification:
+
+```
+Note: Learnings threshold met — {key}: {trigger}. Consider implementing the deferred feature.
+```
+
 8. **Git tag:**
    ```bash
    git tag -a {version} -m "Milestone: {name}"
@@ -423,6 +445,38 @@ Archive a completed milestone and prepare for the next one.
    git commit -m "docs(planning): complete milestone {version}"
    ```
 
+9b. **Push milestone to remote:**
+
+Use AskUserQuestion to ask the user how they want to publish the milestone:
+
+```
+question: "How should this milestone be published to GitHub?"
+header: "Publish"
+options:
+  - label: "Push tag + commits"    description: "Push the v{version} tag and any unpushed commits to origin"
+  - label: "Skip for now"          description: "Keep everything local — push later manually"
+```
+
+- If "Push tag + commits": run `git push origin main --follow-tags` to push both commits and the annotated tag in one command. Display success or error.
+- If "Skip for now": display reminder: "Tag v{version} is local only. Push when ready: `git push origin main --follow-tags`"
+- If "Other": follow user instructions (e.g., create a PR, push to a different branch, etc.)
+
+### Post-Completion Smoke Test
+
+If `config.deployment.smoke_test_command` is set and non-empty:
+
+1. Run the command via Bash
+2. If exit code 0: display "Smoke test passed" with command output
+3. If exit code non-zero: display advisory warning:
+
+   ```
+   ⚠ Smoke test failed (exit code {N})
+   Command: {smoke_test_command}
+   Output: {first 20 lines of output}
+   ```
+
+   This is advisory only — the milestone is already archived. Surface it as a potential issue for the user to investigate.
+
 10. **Confirm** with branded output:
     ```
     ╔══════════════════════════════════════════════════════════════╗

package/plugins/copilot-pbr/templates/pr-body.md.tmpl

@@ -0,0 +1,22 @@
+## Phase <%= phase_number %>: <%= phase_name %>
+
+**Goal**: <%= phase_goal %>
+
+### Key Files Changed
+<% key_files.forEach(f => { %>
+- `<%= f %>`
+<% }) %>
+
+### Verification
+- Status: <%= verification_status %>
+- Must-haves: <%= must_haves_passed %>/<%= must_haves_total %> passed
+
+<% if (closes_issues && closes_issues.length > 0) { %>
+### Issues
+<% closes_issues.forEach(n => { %>
+Closes #<%= n %>
+<% }) %>
+<% } %>
+
+---
+*Generated by [Plan-Build-Run](https://github.com/SienkLogic/plan-build-run)*

package/plugins/cursor-pbr/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "pbr",
   "displayName": "Plan-Build-Run",
-  "version": "2.38.1",
+  "version": "2.40.0",
   "description": "Plan-Build-Run — Structured development workflow for Cursor. Solves context rot through disciplined subagent delegation, structured planning, atomic execution, and goal-backward verification.",
   "author": {
     "name": "SienkLogic",

package/plugins/cursor-pbr/agents/executor.md

@@ -113,6 +113,19 @@ One task = one commit. Exception: TDD tasks get 3 commits (RED, GREEN, REFACTOR)
 
 Stage only files listed in the task's `<files>`. If git commit fails with lock error, retry up to 3 times with 2s delay.
 
+### Issue Auto-Close
+
+When the plan frontmatter contains a non-empty `closes_issues` array, append issue-closing syntax to the **final** commit body for the plan:
+
+```
+git commit -m "feat(01-02): implement user auth
+
+Closes #42
+Closes #57"
+```
+
+Only append to the LAST commit of the plan — intermediate commits (RED/GREEN in TDD, partial progress) should NOT include closing syntax.
+
 ---
 
 ## Deviation Rules

package/plugins/cursor-pbr/references/config-reference.md

@@ -156,11 +156,23 @@ Controls git integration and branching strategy.
 | `phase_branch_template` | string | `plan-build-run/phase-{phase}-{slug}` | Phase branch name pattern |
 | `milestone_branch_template` | string | `plan-build-run/{milestone}-{slug}` | Milestone branch name pattern |
 | `mode` | string | `enabled` | Git mode: `enabled` or `disabled` |
+| `auto_pr` | boolean | `false` | Create a GitHub PR after successful phase verification when branching is enabled |
 
 When `git.mode` is `disabled`, no git commands run at all -- no commits, branching, or hook validation. Useful for prototyping or non-git projects. See `references/git-integration.md` for full branching strategy details.
 
 ---
 
+## ci
+
+Controls CI integration for build gates.
+
+| Property | Type | Default | Description |
+|----------|------|---------|-------------|
+| `ci.gate_enabled` | boolean | `false` | Block wave advancement until CI passes |
+| `ci.wait_timeout_seconds` | number | `120` | Max seconds to wait for CI completion |
+
+---
+
 ## gates
 
 Confirmation gates that pause execution to ask the user before proceeding. Setting a gate to `false` makes that step automatic.
@@ -220,6 +232,16 @@ This value is overridden by the active depth profile if a `depth_profiles` entry
 
 ---
 
+## deployment
+
+Controls post-milestone deployment verification.
+
+| Property | Type | Default | Description |
+|----------|------|---------|-------------|
+| `deployment.smoke_test_command` | string | `""` | Bash command to run after milestone completion (e.g., `"curl -sf https://myapp.com/health"`) |
+
+---
+
 ## depth_profiles
 
 Override the built-in depth profile defaults. Each key (`quick`, `standard`, `comprehensive`) maps to an object of settings that take effect when that depth is active.

package/plugins/cursor-pbr/references/git-integration.md

@@ -175,6 +175,36 @@ Branch name templates are configured in `config.json`:
 - `git.phase_branch_template`: Default `plan-build-run/phase-{phase}-{slug}`
 - `git.milestone_branch_template`: Default `plan-build-run/{milestone}-{slug}`
 
+### PR Creation
+
+When `git.auto_pr: true` and `git.branching` is `phase` or `milestone`, the build skill creates a GitHub PR after verification passes:
+
+1. Push the phase branch to the remote
+2. Create a PR via `gh pr create` with structured title and body
+3. PR title follows the commit convention: `feat(phase-{N}): {phase slug}`
+4. PR body includes phase goal, key files changed, and must-have verification results
+
+When `git.auto_pr: false` (default), the build skill offers the user a choice after verification:
+- Create PR now
+- Skip PR creation
+- Push branch only (create PR later)
+
+PR creation requires `gh` CLI authenticated with repo write access.
+
+### CI Integration
+
+When `ci.gate_enabled: true`, the build skill checks GitHub Actions status after each wave completes:
+
+1. Run: `gh run list --branch $(git branch --show-current) --limit 1 --json status,conclusion,url`
+2. If `status == completed` and `conclusion == success`: proceed to next wave
+3. If `status == in_progress`: wait up to `ci.wait_timeout_seconds`, re-check
+4. If `conclusion != success` or timeout: surface warning with run URL and offer:
+   - **Wait**: continue polling
+   - **Continue anyway**: proceed despite CI failure (logged as deviation)
+   - **Abort**: stop the build
+
+CI gate requires `gh` CLI and GitHub Actions configured on the repository. The gate only activates when there are commits pushed to a remote branch (branching must be enabled).
+
 ### Git Mode
 
 The `git.mode` field controls whether git integration is active:

package/plugins/cursor-pbr/references/plan-format.md

@@ -47,6 +47,9 @@ consumes:
 requirement_ids:
   - "P02-G1"
   - "P02-G2"
+closes_issues:
+  - 42
+  - 57
 ---
 ```
 
@@ -72,6 +75,7 @@ requirement_ids:
 | `requirement_ids` | NO | array | Requirement IDs from REQUIREMENTS.md or ROADMAP.md goal IDs that this plan addresses. Enables bidirectional traceability between plans and requirements/goals. |
 | `dependency_fingerprints` | NO | object | Hashes of dependency phase SUMMARY.md files at plan-creation time. Used to detect stale plans. |
 | `data_contracts` | NO | array | Cross-boundary parameter mappings for calls where arguments originate from external boundaries. Format: `"param: source (context) [fallback]"` |
+| `closes_issues` | NO | number[] | GitHub issue numbers to close when this plan's final commit lands. Default: `[]` |
 
 ### Data Contracts
 

package/plugins/cursor-pbr/skills/begin/SKILL.md

@@ -212,6 +212,25 @@ Spawn parallel agents for research. Each researcher writes to `.planning/researc
 
 **CRITICAL: Create .planning/research/ directory NOW before spawning researchers. Do NOT skip this step.**
 
+**Learnings injection (opt-in):** Before spawning researchers, check if global learnings exist:
+
+```bash
+node {resolved_plugin_root}/scripts/pbr-tools.js learnings query --tags "stack,tech" 2>/dev/null
+```
+
+If the command succeeds AND returns a non-empty JSON array:
+
+- Write the results to a temp file:
+
+  ```bash
+  node {resolved_plugin_root}/scripts/pbr-tools.js learnings query --tags "stack,tech" > /tmp/pbr-learnings-$$.md
+  ```
+
+- Note the temp file path as `{learnings_temp_path}`
+- Add this file to the researcher's `files_to_read` block (see below)
+
+If no learnings exist or the command fails: skip injection silently.
+
 **For each research topic, invoke the @researcher agent:**
 
 Invoke `@researcher` with the research prompt constructed from the template.
@@ -231,9 +250,12 @@ Read `skills/begin/templates/researcher-prompt.md.tmpl` for the prompt structure
 <files_to_read>
 CRITICAL: Read these files BEFORE any other action:
 1. .planning/REQUIREMENTS.md — scoped requirements (if exists)
+{if learnings_temp_path exists}2. {learnings_temp_path} — cross-project learnings (tech stack patterns from past PBR projects){/if}
 </files_to_read>
 ```
 
+If `{learnings_temp_path}` was produced in the learnings injection step above, replace `{if...}{/if}` with the actual line. If no learnings were found, omit line 2 entirely.
+
 **Placeholders to fill:**
 - `{project name from questioning}` — project name gathered in Step 2
 - `{2-3 sentence description from questioning}` — project description from Step 2

package/plugins/cursor-pbr/skills/build/SKILL.md

@@ -615,6 +615,26 @@ Resume at: Task {N+1} (or re-execute checkpoint task with user's answer)
 Continue execution from the checkpoint. Skip completed tasks. Process the checkpoint resolution, then continue with remaining tasks. Write SUMMARY.md when done.
 ```
 
+#### 6e-ii. CI Gate (after wave completion, conditional)
+
+If `config.ci.gate_enabled` is `true` AND `config.git.branching` is not `none`:
+
+1. Push current commits: `git push`
+2. Wait 5 seconds for CI to trigger
+3. Check: `gh run list --branch $(git branch --show-current) --limit 1 --json status,conclusion,url`
+4. If in_progress: poll every 15 seconds up to `config.ci.wait_timeout_seconds`
+5. If failed/timed out: show warning box:
+
+   ```
+   ⚠ CI Status: {conclusion}
+   Run: {url}
+   Options: [Wait] [Continue anyway] [Abort]
+   ```
+
+6. Use AskUserQuestion to present options: Wait / Continue anyway / Abort
+7. If "Continue anyway": log deviation — `DEVIATION: CI gate bypassed for wave {N}`
+8. If "Abort": stop build, update STATE.md
+
 #### 6f. Update STATE.md
 
 After each wave completes (all plans in the wave are done, skipped, or aborted):
@@ -790,6 +810,31 @@ If `git.branching` is `phase`:
 - If "Yes, merge": complete the merge and delete the phase branch
 - If "No, keep" or "Other": leave the branch as-is and inform the user
 
+**8d-ii. PR Creation (when branching enabled):**
+
+If `config.git.branching` is `phase` or `milestone` AND phase verification passed:
+
+1. Push the phase branch: `git push -u origin {branch-name}`
+2. If `config.git.auto_pr` is `true`:
+   - Run: `gh pr create --title "feat({phase-scope}): {phase-slug}" --body "$(cat <<'EOF'
+## Phase {N}: {phase name}
+
+**Goal**: {phase goal from ROADMAP.md}
+
+### Key Files
+{key_files from SUMMARY.md, bulleted}
+
+### Verification
+{pass/fail status from VERIFICATION.md}
+
+---
+Generated by Plan-Build-Run
+EOF
+)"`
+3. If `config.git.auto_pr` is `false`:
+   - Use AskUserQuestion to ask: "Phase branch pushed. Create a PR?"
+   - Options: Yes (create PR as above) / No / Later (skip)
+
 **8e. Auto-advance / auto-continue (conditional):**
 
 **If `features.auto_advance` is `true` AND `mode` is `autonomous`:**

package/plugins/cursor-pbr/skills/explore/SKILL.md

@@ -116,6 +116,19 @@ When a knowledge gap emerges during the conversation — you're unsure about a l
 
 Display to the user: `◐ Spawning researcher...`
 
+**Learnings injection (opt-in):** Check for relevant tech stack learnings:
+
+```bash
+node {resolved_plugin_root}/scripts/pbr-tools.js learnings query --tags "stack,tech" 2>/dev/null
+```
+
+If non-empty JSON array returned:
+
+- Write to temp file: `node {resolved_plugin_root}/scripts/pbr-tools.js learnings query --tags "stack,tech" > /tmp/pbr-learnings-$$.md`
+- Note path as `{learnings_temp_path}`; add as item 3 in the researcher's `files_to_read` block below
+
+If no learnings or command fails: omit the extra files_to_read entry.
+
 ```
 Task({
   subagent_type: "pbr:researcher",
@@ -123,6 +136,7 @@ Task({
     CRITICAL: Read these files BEFORE any other action:
     1. .planning/CONTEXT.md — locked decisions and constraints (if exists)
     2. .planning/STATE.md — current project state (if exists)
+    {if learnings_temp_path exists}3. {learnings_temp_path} — cross-project learnings (tech stack patterns from past PBR projects){/if}
   </files_to_read>
   <research_assignment>
     Topic: {specific research question}
@@ -136,6 +150,9 @@ Task({
 })
 ```
 
+If `{learnings_temp_path}` was produced above, replace `{if...}{/if}` with the actual line. If no learnings were found, omit item 3 entirely.
+```
+
 After the researcher completes, check for completion markers in the Task() output:
 
 - If `## RESEARCH COMPLETE` is present: proceed normally