create-agdf 0.2.0 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (9) hide show
  1. package/generated/.github/skills/agdf-brownfield-analysis/SKILL.md +3 -1
  2. package/generated/.github/skills/agdf-gate-check/SKILL.md +5 -1
  3. package/generated/AGENTS.md +5 -2
  4. package/generated/plugins/agdf/.codex-plugin/plugin.json +1 -1
  5. package/generated/plugins/agdf/meta/agdf-agent-router.md +5 -2
  6. package/generated/plugins/agdf/meta/agdf-plugin.definition.json +4 -4
  7. package/generated/plugins/agdf/skills/brownfield-analysis/SKILL.md +3 -1
  8. package/generated/plugins/agdf/skills/gate-check/SKILL.md +5 -1
  9. package/package.json +1 -1
package/generated/.github/skills/agdf-brownfield-analysis/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: agdf-brownfield-analysis
3
- 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.
3
+ 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.
4
4
  ---
5
5
 
6
6
  # brownfield-analysis
@@ -38,6 +38,7 @@ Brownfield-specific output must make evidence, missing existing-system view, par
38
38
  12. Specification archive migrations must follow the archive index if present.
39
39
 
40
40
  ## When To Use
41
+ - after `agdf-gate-check` permits implementation preparation or live `.agdf/control/AGDF_RUN.md` already names Brownfield Analysis as the next allowed action
41
42
  - before `CD+Tests`
42
43
  - before changes to an existing repository
43
44
  - bug fixes in existing modules
@@ -58,6 +59,7 @@ Use what is available:
58
59
  - repository conventions
59
60
 
60
61
  If inputs are missing, work only from observable evidence and mark gaps explicitly.
62
+ If gate status, approval, scope or next allowed action is unclear, stop and route to `agdf-gate-check` instead of recommending or starting implementation.
61
63
 
62
64
  ## Workflow
63
65
  1. Identify affected tasks and scope.
package/generated/.github/skills/agdf-gate-check/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: agdf-gate-check
3
- 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.
3
+ 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.
4
4
  ---
5
5
 
6
6
  # gate-check
@@ -54,6 +54,7 @@ Internal mandatory steps:
54
54
  `Brownfield Analysis -> CD+Tests -> CR -> OR`
55
55
 
56
56
  ## When To Use
57
+ - new user intent to build, add, change, extend, refactor or deliver something
57
58
  - Structured Delivery before first artefact creation
58
59
  - unclear current gate
59
60
  - user says "continue" or similar without exact approval
@@ -63,6 +64,9 @@ Internal mandatory steps:
63
64
 
64
65
  Not required for simple Quick Tasks without new product scope and without formal artefacts.
65
66
 
67
+ For a fresh prompt such as "I want to build a small CLI", use this skill first.
68
+ 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.
69
+
66
70
  ## Inputs
67
71
  Use what is available:
68
72
 
package/generated/AGENTS.md CHANGED
@@ -23,6 +23,8 @@ Therefore generated Copilot skill names use the AGDF prefix:
23
23
  Do not remove that prefix in Copilot-facing repository skills.
24
24
  Codex and Claude Code plugin surfaces use the same canonical router with unprefixed skill names because their plugin namespace already carries `agdf`.
25
25
  ## Mode Selection
26
+ 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.
27
+
26
28
  Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics.
27
29
 
28
30
  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.
33
35
  ## Skill Routing
34
36
  | Skill | Use For | Boundary |
35
37
  |---|---|---|
36
- | `agdf-brownfield-analysis` | before non-trivial implementation in existing systems | clarifies reuse, owners and risks |
38
+ | `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 |
37
39
  | `agdf-clean-implementation-review` | inspect workarounds, fallbacks, parallel structures or symptom fixes | not a TP or QA substitute |
38
40
  | `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 |
39
41
  | `agdf-delivery-closeout` | commit/PR-near handoff after QA/OR/UAT | never performs VCS actions automatically |
40
- | `agdf-gate-check` | unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts |
42
+ | `agdf-gate-check` | new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts |
41
43
  | `agdf-qa-gate` | final QA decision | only instance for `pass | revise | block` |
42
44
  | `agdf-release-or` | auditable closeout for every relevant run | not a QA substitute |
43
45
  | `agdf-task-plan-review` | after implementation and before QA, verify TP coverage | no final QA decision |
44
46
 
45
47
  Select exactly one primary skill first.
46
48
  Add more only when they cover a distinct concrete risk dimension.
49
+ 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.
47
50
 
48
51
  ## Runtime Contract
49
52
  For repeated output, gate, Quality Contract and Context Graph rules, use:
package/generated/plugins/agdf/.codex-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agdf",
3
- "version": "0.2.0",
3
+ "version": "0.2.2",
4
4
  "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
5
5
  "author": {
6
6
  "name": "AI-native Governance & Delivery Framework",
package/generated/plugins/agdf/meta/agdf-agent-router.md CHANGED
@@ -24,6 +24,8 @@ Do not duplicate the plugin namespace in Codex or Claude Code plugin skill names
24
24
  That `agdf-` prefix is reserved for GitHub Copilot repository skills, where no plugin namespace exists.
25
25
 
26
26
  ## Mode Selection
27
+ 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.
28
+
27
29
  Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics.
28
30
 
29
31
  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.
34
36
  ## Skill Routing
35
37
  | Skill | Use For | Boundary |
36
38
  |---|---|---|
37
- | `brownfield-analysis` | before non-trivial implementation in existing systems | clarifies reuse, owners and risks |
39
+ | `brownfield-analysis` | after gate-check permits implementation preparation, before non-trivial changes in existing systems | clarifies reuse, owners and risks; never bypasses gate-check |
38
40
  | `clean-implementation-review` | inspect workarounds, fallbacks, parallel structures or symptom fixes | not a TP or QA substitute |
39
41
  | `code-review` | mandatory CR step after code changes, focused on defects, regression and security findings | does not replace TP review, clean review or QA |
40
42
  | `delivery-closeout` | commit/PR-near handoff after QA/OR/UAT | never performs VCS actions automatically |
41
- | `gate-check` | unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts |
43
+ | `gate-check` | new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested | does not create later artefacts |
42
44
  | `qa-gate` | final QA decision | only instance for `pass | revise | block` |
43
45
  | `release-or` | auditable closeout for every relevant run | not a QA substitute |
44
46
  | `task-plan-review` | after implementation and before QA, verify TP coverage | no final QA decision |
45
47
 
46
48
  Select exactly one primary skill first.
47
49
  Add more only when they cover a distinct concrete risk dimension.
50
+ 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.
48
51
 
49
52
  ## Runtime Contract
50
53
  For repeated output, gate, Quality Contract and Context Graph rules, use:
package/generated/plugins/agdf/meta/agdf-plugin.definition.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
3
  "id": "agdf",
4
- "version": "0.2.0",
4
+ "version": "0.2.2",
5
5
  "displayName": "AI Governance & Delivery Framework",
6
6
  "developerName": "AI-native Governance & Delivery Framework",
7
7
  "description": "Codex-first workflow skills for gated, auditable AI-assisted software delivery.",
@@ -42,8 +42,8 @@
42
42
  "skillSet": [
43
43
  {
44
44
  "slug": "brownfield-analysis",
45
- "useFor": "before non-trivial implementation in existing systems",
46
- "boundary": "clarifies reuse, owners and risks"
45
+ "useFor": "after gate-check permits implementation preparation, before non-trivial changes in existing systems",
46
+ "boundary": "clarifies reuse, owners and risks; never bypasses gate-check"
47
47
  },
48
48
  {
49
49
  "slug": "clean-implementation-review",
@@ -62,7 +62,7 @@
62
62
  },
63
63
  {
64
64
  "slug": "gate-check",
65
- "useFor": "unclear approval, Structured Delivery, later-gate artefact requested",
65
+ "useFor": "new build/change intent, unclear approval, Structured Delivery, later-gate artefact requested",
66
66
  "boundary": "does not create later artefacts"
67
67
  },
68
68
  {
package/generated/plugins/agdf/skills/brownfield-analysis/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: brownfield-analysis
3
- 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.
3
+ 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.
4
4
  ---
5
5
 
6
6
  # brownfield-analysis
@@ -38,6 +38,7 @@ Brownfield-specific output must make evidence, missing existing-system view, par
38
38
  12. Specification archive migrations must follow the archive index if present.
39
39
 
40
40
  ## When To Use
41
+ - after `gate-check` permits implementation preparation or live `.agdf/control/AGDF_RUN.md` already names Brownfield Analysis as the next allowed action
41
42
  - before `CD+Tests`
42
43
  - before changes to an existing repository
43
44
  - bug fixes in existing modules
@@ -58,6 +59,7 @@ Use what is available:
58
59
  - repository conventions
59
60
 
60
61
  If inputs are missing, work only from observable evidence and mark gaps explicitly.
62
+ If gate status, approval, scope or next allowed action is unclear, stop and route to `gate-check` instead of recommending or starting implementation.
61
63
 
62
64
  ## Workflow
63
65
  1. Identify affected tasks and scope.
package/generated/plugins/agdf/skills/gate-check/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: gate-check
3
- 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.
3
+ 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.
4
4
  ---
5
5
 
6
6
  # gate-check
@@ -54,6 +54,7 @@ Internal mandatory steps:
54
54
  `Brownfield Analysis -> CD+Tests -> CR -> OR`
55
55
 
56
56
  ## When To Use
57
+ - new user intent to build, add, change, extend, refactor or deliver something
57
58
  - Structured Delivery before first artefact creation
58
59
  - unclear current gate
59
60
  - user says "continue" or similar without exact approval
@@ -63,6 +64,9 @@ Internal mandatory steps:
63
64
 
64
65
  Not required for simple Quick Tasks without new product scope and without formal artefacts.
65
66
 
67
+ For a fresh prompt such as "I want to build a small CLI", use this skill first.
68
+ 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.
69
+
66
70
  ## Inputs
67
71
  Use what is available:
68
72
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-agdf",
3
- "version": "0.2.0",
3
+ "version": "0.2.2",
4
4
  "description": "Bootstrap AGDF repository-local plugin files, Copilot instructions, skills, control files and machine-readable checks.",
5
5
  "type": "module",
6
6
  "files": [