@rasensio/aidlc-content 1.17.0 → 1.19.0

package/capabilities/copilot.yaml

@@ -0,0 +1,9 @@
+platform: copilot
+capabilities:
+  plan-mode:
+    phases: [ideation, requirements, design]
+    activation: >-
+      Switch Copilot to plan mode for this phase (the agent picker in the Chat
+      view, or `agent: plan`). Produce the phase artifact as a written plan and
+      have it agreed before any file is edited — these phases decide what to
+      build, not how to type it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rasensio/aidlc-content",
-  "version": "1.17.0",
+  "version": "1.19.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/skills/03-entry-point.md

@@ -9,6 +9,10 @@ native_mode_hint:
     This skill is an interactive entry point, not a phase artifact. Do not
     enter plan mode. Read lifecycle state, present the menu, and wait for
     the user's choice before doing any work.
+  copilot: >-
+    This skill is an interactive entry point, not a phase artifact. Stay in the
+    default agent — do not switch to plan mode. Read lifecycle state, present the
+    menu, and wait for the user's choice before doing any work.
 ---
 # AIDLC Entry Point
 

package/skills/04-roadmap.md

@@ -9,6 +9,10 @@ native_mode_hint:
     This skill is an interactive inbox, not a phase artifact. Do not enter
     plan mode. Capture is a single write-and-confirm; never touch instance
     state while capturing.
+  copilot: >-
+    This skill is an interactive inbox, not a phase artifact. Stay in the default
+    agent — do not switch to plan mode. Capture is a single write-and-confirm;
+    never touch instance state while capturing.
 ---
 # Roadmap
 

package/skills/05-constitution.md

@@ -10,6 +10,11 @@ native_mode_hint:
     not enter plan mode. Never rewrite an existing constitution from the vision
     in one step — propose changes into the inbox and apply only what the user
     accepts.
+  copilot: >-
+    This skill imports a document and drafts prose for the user to correct. Stay
+    in the default agent — do not switch to plan mode. Never rewrite an existing
+    constitution from the vision in one step — propose changes into the inbox and
+    apply only what the user accepts.
 ---
 # Constitution
 

package/skills/60-deployment.md

@@ -39,12 +39,20 @@ deployment checklist.
    - Deployment steps in order
    - Rollback procedure
    - Monitoring and verification steps post-deploy
-4. **Pre-deployment checks.** Verify:
+4. **Update the affected topic page in `docs/`.** If this instance changed how a documented topic
+   behaves — its interface, its failure modes, or the reason it is built the way it is — update that
+   topic's page before releasing, and say in the deployment artifact which page you touched or that
+   none applied. The manifest at `docs/index.yaml` maps each topic to the code it documents, so
+   start there to find the page. A design reason bought with a bugfix belongs in the page's "why"
+   section: the knowledge graph records what the code looks like and cannot afford to record why, so
+   a reason that lives nowhere else is one the next agent will simplify away. This is a checklist
+   step, not a gate — no phase is blocked on it.
+5. **Pre-deployment checks.** Verify:
    - CI pipeline passes
    - No critical findings open from adversarial reviews
    - Dependencies are pinned and audited
-5. **Execute deployment.** Follow the release plan step by step.
-6. **Verify.** Confirm the deployment succeeded using the monitoring steps.
+6. **Execute deployment.** Follow the release plan step by step.
+7. **Verify.** Confirm the deployment succeeded using the monitoring steps.
 
 ## Exit Criteria