@pigcloud/skills 1.0.4 → 1.0.6
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.
- package/CHANGELOG.md +29 -28
- package/README.en.md +4 -3
- package/README.md +37 -35
- package/bin/cli.js +98 -71
- package/package.json +69 -69
- package/rules/coding/implementation.md +6 -5
- package/rules/product/project-context.md +6 -5
- package/rules/skill-profile-map.json +6 -5
- package/rules/skill-profile-map.md +6 -5
- package/scripts/ci-validator.sh +19 -19
- package/scripts/validate-skill-shapes.js +5 -4
- package/scripts/validate-skills.ps1 +6 -6
- package/scripts/validate-skills.sh +5 -5
- package/skills/{api-docs → api-contract-docs}/SKILL.md +5 -4
- package/skills/{extract-business-facts → business-fact-extraction}/SKILL.md +9 -8
- package/skills/{extract-business-facts → business-fact-extraction}/scripts/write-knowledge-base.js +4 -3
- package/skills/code-review/SKILL.md +7 -6
- package/skills/domain-modeling/SKILL.md +4 -3
- package/skills/feature-build/SKILL.md +10 -10
- package/skills/feature-build/references/comment-specification.md +1 -1
- package/skills/knowledge-capture/SKILL.md +1 -1
- package/skills/{performance-check → performance-audit}/SKILL.md +5 -4
- package/skills/project-bootstrap/SKILL.md +3 -2
- package/skills/references/business-fact-extraction.md +9 -8
- package/skills/references/engineering-delivery-method.md +4 -3
- package/skills/references/engineering-delivery-template.md +3 -2
- package/skills/references/golden-prompt-suite.js +44 -43
- package/skills/references/project-requirement-alignment.md +2 -1
- package/skills/references/rule-loading-map.md +4 -3
- package/skills/references/skill-authoring-standard.md +4 -3
- package/skills/references/skill-reference-matrix.md +15 -14
- package/skills/{security-review → security-audit}/SKILL.md +4 -2
- package/skills/{spec → spec-refinement}/SKILL.md +19 -18
- package/skills/technical-design/SKILL.md +11 -10
- package/skills/test-design/SKILL.md +2 -1
|
@@ -4,7 +4,7 @@ description: 当模块、接口或依赖仍需决策时,在稳定规格基础
|
|
|
4
4
|
lifecycle_stage: design
|
|
5
5
|
rule_profile: analysis
|
|
6
6
|
dependencies:
|
|
7
|
-
- spec
|
|
7
|
+
- spec-refinement
|
|
8
8
|
triggers:
|
|
9
9
|
- architecture decision
|
|
10
10
|
- module split
|
|
@@ -12,7 +12,7 @@ triggers:
|
|
|
12
12
|
- dependency direction
|
|
13
13
|
- design boundary
|
|
14
14
|
inputs:
|
|
15
|
-
- executable spec
|
|
15
|
+
- executable spec-refinement
|
|
16
16
|
- selected rules bundle
|
|
17
17
|
- existing module context
|
|
18
18
|
outputs:
|
|
@@ -21,7 +21,7 @@ outputs:
|
|
|
21
21
|
- interface contract
|
|
22
22
|
- implementation constraints
|
|
23
23
|
workflow:
|
|
24
|
-
- confirm the spec is stable enough for design work
|
|
24
|
+
- confirm the spec-refinement is stable enough for design work
|
|
25
25
|
- define boundaries, dependencies, and interfaces
|
|
26
26
|
- map design decisions to the rules bundle
|
|
27
27
|
- hand off to feature-build
|
|
@@ -42,7 +42,7 @@ refs:
|
|
|
42
42
|
|
|
43
43
|
## Purpose
|
|
44
44
|
|
|
45
|
-
Turn a stable spec into concrete architecture and implementation boundaries.
|
|
45
|
+
Turn a stable spec-refinement into concrete architecture and implementation boundaries.
|
|
46
46
|
|
|
47
47
|
## Suitable / Unsuitable
|
|
48
48
|
|
|
@@ -51,15 +51,15 @@ Turn a stable spec into concrete architecture and implementation boundaries.
|
|
|
51
51
|
|
|
52
52
|
## Quick Start
|
|
53
53
|
|
|
54
|
-
- Start from the stable spec and isolate the decisions that affect boundaries or dependencies.
|
|
54
|
+
- Start from the stable spec-refinement and isolate the decisions that affect boundaries or dependencies.
|
|
55
55
|
- Load the smallest rules bundle that matches the current task context.
|
|
56
56
|
- Turn design choices into implementation constraints, not code.
|
|
57
|
-
- If the spec is still unstable, stop and return to `spec`.
|
|
57
|
+
- If the spec-refinement is still unstable, stop and return to `spec-refinement`.
|
|
58
58
|
|
|
59
59
|
## Inputs / Outputs
|
|
60
60
|
|
|
61
61
|
- Inputs:
|
|
62
|
-
- executable spec
|
|
62
|
+
- executable spec-refinement
|
|
63
63
|
- selected rules bundle
|
|
64
64
|
- existing module context
|
|
65
65
|
- Outputs:
|
|
@@ -70,9 +70,9 @@ Turn a stable spec into concrete architecture and implementation boundaries.
|
|
|
70
70
|
|
|
71
71
|
## Workflow
|
|
72
72
|
|
|
73
|
-
1. Confirm the spec is stable enough for design work.
|
|
73
|
+
1. Confirm the spec-refinement is stable enough for design work.
|
|
74
74
|
2. Define boundaries, dependencies, and interfaces.
|
|
75
|
-
3. Route scope gaps back to `spec` instead of forcing design decisions.
|
|
75
|
+
3. Route scope gaps back to `spec-refinement` instead of forcing design decisions.
|
|
76
76
|
4. Map design decisions to the rules bundle.
|
|
77
77
|
5. Produce implementation constraints for `feature-build`.
|
|
78
78
|
|
|
@@ -89,7 +89,7 @@ Turn a stable spec into concrete architecture and implementation boundaries.
|
|
|
89
89
|
- Do not skip rule loading when rule constraints matter.
|
|
90
90
|
- Do not output full code or pseudo-code as the design artifact.
|
|
91
91
|
- Do not collapse boundaries just to reduce context.
|
|
92
|
-
- Do not keep working if the spec is not stable enough to design.
|
|
92
|
+
- Do not keep working if the spec-refinement is not stable enough to design.
|
|
93
93
|
|
|
94
94
|
## Stop Rules
|
|
95
95
|
|
|
@@ -103,3 +103,4 @@ Turn a stable spec into concrete architecture and implementation boundaries.
|
|
|
103
103
|
- `skills/references/rule-loading-map.md`
|
|
104
104
|
- `skills/references/flow-test-cases.md`
|
|
105
105
|
- `rules/index.md`
|
|
106
|
+
|
|
@@ -14,7 +14,7 @@ triggers:
|
|
|
14
14
|
- verification
|
|
15
15
|
inputs:
|
|
16
16
|
- implementation notes
|
|
17
|
-
- executable spec
|
|
17
|
+
- executable spec-refinement
|
|
18
18
|
- design constraints
|
|
19
19
|
- self-test evidence
|
|
20
20
|
outputs:
|
|
@@ -89,3 +89,4 @@ Design and validate test coverage for the implemented change.
|
|
|
89
89
|
- `skills/references/engineering-delivery-method.md`
|
|
90
90
|
- `skills/references/engineering-delivery-template.md`
|
|
91
91
|
- `rules/index.md`
|
|
92
|
+
|