create-agdf 0.1.9 → 0.2.2

package/README.md

@@ -1,6 +1,6 @@
 # create-agdf
 
-Bootstrap AGDF repository instructions for one repository.
+Bootstrap AGDF repository instructions and a machine-checkable control loop for one repository.
 
 ## Usage
 
@@ -72,6 +72,8 @@ npm create agdf@latest gate-check --json
 
 The gate check reports `open | blocked`, the current gate, blocking reason, missing exact approval, allowed outputs, forbidden outputs, next allowed action, evidence references and the embedded doctor report.
 
+Together, `init`, `doctor` and `gate-check --json` turn AGDF from an instruction layer into a repository control system: the agent can be guided by rules, and the repository state can be checked before the next governed step.
+
 ## Single source of truth
 
 The repository-facing AGDF sources are maintained in:

package/generated/.github/skills/agdf-brownfield-analysis/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: agdf-brownfield-analysis
-description: Use this skill before implementation in an existing codebase, especially for feature extensions, bug fixes, refactorings, or changes to existing modules. It analyzes existing artefacts, current coverage, reuse strategy, risks, and the minimal clean implementation path. Use it before CD+Tests.
+description: Use this skill after gate-check or live AGDF control state confirms that implementation preparation is allowed, and before non-trivial implementation in an existing codebase. It analyzes existing artefacts, current coverage, reuse strategy, risks, and the minimal clean implementation path. Do not use it as the first AGDF skill for a fresh "I want to build/change X" prompt when approval, scope, or next allowed action is unclear.
 ---
 
 # brownfield-analysis
@@ -38,6 +38,7 @@ Brownfield-specific output must make evidence, missing existing-system view, par
 12. Specification archive migrations must follow the archive index if present.
 
 ## When To Use
+- after `agdf-gate-check` permits implementation preparation or live `.agdf/control/AGDF_RUN.md` already names Brownfield Analysis as the next allowed action
 - before `CD+Tests`
 - before changes to an existing repository
 - bug fixes in existing modules
@@ -58,6 +59,7 @@ Use what is available:
 - repository conventions
 
 If inputs are missing, work only from observable evidence and mark gaps explicitly.
+If gate status, approval, scope or next allowed action is unclear, stop and route to `agdf-gate-check` instead of recommending or starting implementation.
 
 ## Workflow
 1. Identify affected tasks and scope.

package/generated/.github/skills/agdf-gate-check/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: agdf-gate-check
-description: Use this skill when the active gate is unclear, when a later-gate artefact is requested, when an exact approval may be missing, or when the next permissible step must be determined. Use it before creating formal artefacts in Structured Delivery and whenever implicit consent might be mistaken for approval.
+description: Use this skill as the default first AGDF skill for any new build, change, extension, refactor, feature, CLI, app, fix with product semantics, Structured Delivery request, unclear approval, later-gate artefact request, or unclear next permissible step. Use it before brownfield-analysis, implementation, formal artefacts, QA, or release when approval/evidence/next action is not already explicit.
 ---
 
 # gate-check
@@ -54,6 +54,7 @@ Internal mandatory steps:
 `Brownfield Analysis -> CD+Tests -> CR -> OR`
 
 ## When To Use
+- new user intent to build, add, change, extend, refactor or deliver something
 - Structured Delivery before first artefact creation
 - unclear current gate
 - user says "continue" or similar without exact approval
@@ -63,6 +64,9 @@ Internal mandatory steps:
 
 Not required for simple Quick Tasks without new product scope and without formal artefacts.
 
+For a fresh prompt such as "I want to build a small CLI", use this skill first.
+Do not route directly to `agdf-brownfield-analysis` or implementation until this skill or live AGDF control state says that implementation preparation is the next allowed action.
+
 ## Inputs
 Use what is available:
 

package/generated/AGENTS.md

@@ -23,6 +23,8 @@ Therefore generated Copilot skill names use the AGDF prefix:
 Do not remove that prefix in Copilot-facing repository skills.
 Codex and Claude Code plugin surfaces use the same canonical router with unprefixed skill names because their plugin namespace already carries `agdf`.
 ## Mode Selection
+Default entry rule: a new user intent to build, add, change, extend, refactor or otherwise deliver something starts with `agdf-gate-check` unless it is clearly only a question, explanation, local inspection, or explicitly scoped review.
+
 Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics.
 
 Use Structured Delivery Mode for new capabilities, architecture, policy, persistence, release-critical work, formal artefacts or explicit approvals.
@@ -33,17 +35,18 @@ Structured Delivery Mode must respect gates, reviews and closeout discipline.
 ## Skill Routing
 | Skill | Use For | Boundary |
 |---|---|---|
-| `agdf-brownfield-analysis` | before non-trivial implementation in existing systems | clarifies reuse, owners and risks |
+| `agdf-brownfield-analysis` | after gate-check permits implementation preparation, before non-trivial changes in existing systems | clarifies reuse, owners and risks; never bypasses gate-check |
 | `agdf-clean-implementation-review` | inspect workarounds, fallbacks, parallel structures or symptom fixes | not a TP or QA substitute |
 | `agdf-code-review` | mandatory CR step after code changes, focused on defects, regression and security findings | does not replace TP review, clean review or QA |
 | `agdf-delivery-closeout` | commit/PR-near handoff after QA/OR/UAT | never performs VCS actions automatically |
-| `agdf-gate-check` | unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts |
+| `agdf-gate-check` | new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts |
 | `agdf-qa-gate` | final QA decision | only instance for `pass | revise | block` |
 | `agdf-release-or` | auditable closeout for every relevant run | not a QA substitute |
 | `agdf-task-plan-review` | after implementation and before QA, verify TP coverage | no final QA decision |
 
 Select exactly one primary skill first.
 Add more only when they cover a distinct concrete risk dimension.
+Do not choose `agdf-brownfield-analysis` as the first primary skill for a fresh "I want to build/change X" prompt unless `agdf-gate-check` or existing live AGDF control state already makes implementation preparation the next allowed action.
 
 ## Runtime Contract
 For repeated output, gate, Quality Contract and Context Graph rules, use:

package/generated/plugins/agdf/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agdf",
-  "version": "0.1.9",
+  "version": "0.2.2",
   "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
   "author": {
     "name": "AI-native Governance & Delivery Framework",
@@ -15,7 +15,7 @@
   "interface": {
     "displayName": "AI Governance & Delivery Framework",
     "shortDescription": "Codex-first workflow skills for gated, auditable AI-assisted delivery.",
-    "longDescription": "AI Governance & Delivery Framework (AGDF) packages reusable Codex-first skills and control templates for gate checks, Brownfield analysis, task-plan review, solution-integrity review, QA decisions, durable run state and auditable delivery closeout.",
+    "longDescription": "AI Governance & Delivery Framework (AGDF) packages reusable Codex-first skills, control templates and machine-readable repository checks for gate decisions, Brownfield analysis, task-plan review, solution-integrity review, QA decisions, durable run state and auditable delivery closeout.",
     "developerName": "AI-native Governance & Delivery Framework",
     "category": "Productivity",
     "capabilities": ["Read", "Write"],

package/generated/plugins/agdf/meta/agdf-agent-router.md

@@ -24,6 +24,8 @@ Do not duplicate the plugin namespace in Codex or Claude Code plugin skill names
 That `agdf-` prefix is reserved for GitHub Copilot repository skills, where no plugin namespace exists.
 
 ## Mode Selection
+Default entry rule: a new user intent to build, add, change, extend, refactor or otherwise deliver something starts with `gate-check` unless it is clearly only a question, explanation, local inspection, or explicitly scoped review.
+
 Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics.
 
 Use Structured Delivery Mode for new capabilities, architecture, policy, persistence, release-critical work, formal artefacts or explicit approvals.
@@ -34,17 +36,18 @@ Structured Delivery Mode must respect gates, reviews and closeout discipline.
 ## Skill Routing
 | Skill | Use For | Boundary |
 |---|---|---|
-| `brownfield-analysis` | before non-trivial implementation in existing systems | clarifies reuse, owners and risks |
+| `brownfield-analysis` | after gate-check permits implementation preparation, before non-trivial changes in existing systems | clarifies reuse, owners and risks; never bypasses gate-check |
 | `clean-implementation-review` | inspect workarounds, fallbacks, parallel structures or symptom fixes | not a TP or QA substitute |
 | `code-review` | mandatory CR step after code changes, focused on defects, regression and security findings | does not replace TP review, clean review or QA |
 | `delivery-closeout` | commit/PR-near handoff after QA/OR/UAT | never performs VCS actions automatically |
-| `gate-check` | unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts |
+| `gate-check` | new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts |
 | `qa-gate` | final QA decision | only instance for `pass | revise | block` |
 | `release-or` | auditable closeout for every relevant run | not a QA substitute |
 | `task-plan-review` | after implementation and before QA, verify TP coverage | no final QA decision |
 
 Select exactly one primary skill first.
 Add more only when they cover a distinct concrete risk dimension.
+Do not choose `brownfield-analysis` as the first primary skill for a fresh "I want to build/change X" prompt unless `gate-check` or existing live AGDF control state already makes implementation preparation the next allowed action.
 
 ## Runtime Contract
 For repeated output, gate, Quality Contract and Context Graph rules, use:

package/generated/plugins/agdf/meta/agdf-plugin.definition.json

@@ -1,13 +1,13 @@
 {
   "schemaVersion": 1,
   "id": "agdf",
-  "version": "0.1.9",
+  "version": "0.2.2",
   "displayName": "AI Governance & Delivery Framework",
   "developerName": "AI-native Governance & Delivery Framework",
   "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
   "claudeDescription": "Codex-first workflow skills and control templates for gated, auditable AI-assisted software delivery.",
   "shortDescription": "Codex-first workflow skills for gated, auditable AI-assisted delivery.",
-  "longDescription": "AI Governance & Delivery Framework (AGDF) packages reusable Codex-first skills and control templates for gate checks, Brownfield analysis, task-plan review, solution-integrity review, QA decisions, durable run state and auditable delivery closeout.",
+  "longDescription": "AI Governance & Delivery Framework (AGDF) packages reusable Codex-first skills, control templates and machine-readable repository checks for gate decisions, Brownfield analysis, task-plan review, solution-integrity review, QA decisions, durable run state and auditable delivery closeout.",
   "homepage": "https://agdf.iself.eu",
   "repository": "https://github.com/arndtgold/ai-native-governance-delivery-framework",
   "license": "Apache-2.0",
@@ -42,8 +42,8 @@
   "skillSet": [
     {
       "slug": "brownfield-analysis",
-      "useFor": "before non-trivial implementation in existing systems",
-      "boundary": "clarifies reuse, owners and risks"
+      "useFor": "after gate-check permits implementation preparation, before non-trivial changes in existing systems",
+      "boundary": "clarifies reuse, owners and risks; never bypasses gate-check"
     },
     {
       "slug": "clean-implementation-review",
@@ -62,7 +62,7 @@
     },
     {
       "slug": "gate-check",
-      "useFor": "unclear approval, Structured Delivery, later-gate artefact requested",
+      "useFor": "new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested",
       "boundary": "does not create later artefacts"
     },
     {

package/generated/plugins/agdf/skills/brownfield-analysis/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: brownfield-analysis
-description: Use this skill before implementation in an existing codebase, especially for feature extensions, bug fixes, refactorings, or changes to existing modules. It analyzes existing artefacts, current coverage, reuse strategy, risks, and the minimal clean implementation path. Use it before CD+Tests.
+description: Use this skill after gate-check or live AGDF control state confirms that implementation preparation is allowed, and before non-trivial implementation in an existing codebase. It analyzes existing artefacts, current coverage, reuse strategy, risks, and the minimal clean implementation path. Do not use it as the first AGDF skill for a fresh "I want to build/change X" prompt when approval, scope, or next allowed action is unclear.
 ---
 
 # brownfield-analysis
@@ -38,6 +38,7 @@ Brownfield-specific output must make evidence, missing existing-system view, par
 12. Specification archive migrations must follow the archive index if present.
 
 ## When To Use
+- after `gate-check` permits implementation preparation or live `.agdf/control/AGDF_RUN.md` already names Brownfield Analysis as the next allowed action
 - before `CD+Tests`
 - before changes to an existing repository
 - bug fixes in existing modules
@@ -58,6 +59,7 @@ Use what is available:
 - repository conventions
 
 If inputs are missing, work only from observable evidence and mark gaps explicitly.
+If gate status, approval, scope or next allowed action is unclear, stop and route to `gate-check` instead of recommending or starting implementation.
 
 ## Workflow
 1. Identify affected tasks and scope.

package/generated/plugins/agdf/skills/gate-check/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gate-check
-description: Use this skill when the active gate is unclear, when a later-gate artefact is requested, when an exact approval may be missing, or when the next permissible step must be determined. Use it before creating formal artefacts in Structured Delivery and whenever implicit consent might be mistaken for approval.
+description: Use this skill as the default first AGDF skill for any new build, change, extension, refactor, feature, CLI, app, fix with product semantics, Structured Delivery request, unclear approval, later-gate artefact request, or unclear next permissible step. Use it before brownfield-analysis, implementation, formal artefacts, QA, or release when approval/evidence/next action is not already explicit.
 ---
 
 # gate-check
@@ -54,6 +54,7 @@ Internal mandatory steps:
 `Brownfield Analysis -> CD+Tests -> CR -> OR`
 
 ## When To Use
+- new user intent to build, add, change, extend, refactor or deliver something
 - Structured Delivery before first artefact creation
 - unclear current gate
 - user says "continue" or similar without exact approval
@@ -63,6 +64,9 @@ Internal mandatory steps:
 
 Not required for simple Quick Tasks without new product scope and without formal artefacts.
 
+For a fresh prompt such as "I want to build a small CLI", use this skill first.
+Do not route directly to `brownfield-analysis` or implementation until this skill or live AGDF control state says that implementation preparation is the next allowed action.
+
 ## Inputs
 Use what is available:
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "create-agdf",
-  "version": "0.1.9",
-  "description": "Bootstrap AGDF repository-local Codex plugin marketplaces, Copilot instructions, skills and control templates.",
+  "version": "0.2.2",
+  "description": "Bootstrap AGDF repository-local plugin files, Copilot instructions, skills, control files and machine-readable checks.",
   "type": "module",
   "files": [
     "bin",