@pigcloud/skills 1.0.0

package/skills/test-design/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: test-design
+description: Design and validate test coverage for an implemented change when regression risk or edge cases need verification
+lifecycle_stage: verify
+rule_profile: testing
+dependencies:
+  - feature-build
+triggers:
+  - test
+  - validation
+  - coverage
+  - regression
+  - edge case
+  - verification
+inputs:
+  - implementation notes
+  - executable spec
+  - design constraints
+  - self-test evidence
+outputs:
+  - test strategy
+  - test cases
+  - regression matrix
+  - validation result
+  - gap report
+workflow:
+  - confirm the implementation scope
+  - review the self-test evidence and implementation notes
+  - design test cases and coverage boundaries
+  - run validation or prepare execution steps
+  - hand off a validation result to code-review
+gates:
+  - stop at verification
+  - do not modify production code
+  - do not rewrite the PRD
+  - do not replace code review
+refs:
+  - skills/references/rule-loading-map.md
+  - skills/references/flow-test-cases.md
+  - skills/references/full-chain-replay-scenarios.md
+  - skills/references/prompt-replay-checklist.md
+  - rules/index.md
+---
+
+# Test Design
+
+## Purpose
+
+Design and validate test coverage for the implemented change.
+
+## Suitable / Unsuitable
+
+- Suitable: test strategy, test cases, coverage, regression, boundary validation
+- Unsuitable: modifying production code, rewriting the PRD, replacing code review
+
+## Workflow
+
+1. Confirm the implementation scope and risk areas.
+2. Review self-test evidence and identify coverage gaps.
+3. Design coverage, boundaries, and regression cases.
+4. Execute or prepare validation steps.
+5. Hand off a validation result to `code-review`.
+
+## Replay Signals
+
+- Input signal: implementation notes, risk areas, coverage gaps, or verification request.
+- Output to verify: test strategy, test cases, regression matrix, validation result, gap report.
+- Stop signal: modifying production code, rewriting the PRD, or replacing code review.
+- Handoff signal: a validation result is ready for `code-review`.
+
+## Examples
+
+- Input: "The feature is implemented; design coverage and run the validation steps."
+- Output: test strategy, test cases, regression matrix, validation result, gap report
+- Stop: do not change production code
+
+## Stop Rules
+
+- Stop at verification.
+- Do not modify production code.
+- Do not rewrite the PRD.
+- Do not replace code review.
+- Do not skip the self-test evidence.
+
+## References
+
+- `skills/references/rule-loading-map.md`
+- `skills/references/flow-test-cases.md`
+- `skills/references/engineering-delivery-method.md`
+- `skills/references/engineering-delivery-template.md`
+- `rules/index.md`

package/skills/workflow-router/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: workflow-router
+description: Route work into the next skill and stage when intent, ownership, or handoff is unclear
+lifecycle_stage: routing
+rule_profile: router
+dependencies: []
+triggers:
+  - unclear stage
+  - unclear intent
+  - next step
+  - route
+  - handoff
+inputs:
+  - user intent
+  - current stage
+  - available artifacts
+outputs:
+  - next skill
+  - stage decision
+  - handoff note
+workflow:
+  - identify the intent type
+  - select the next stage and skill
+  - attach the needed inputs
+  - hand off to the target skill
+gates:
+  - stop after routing
+  - do not perform the target skill's work
+  - do not add rule details
+refs:
+  - skills/references/skill-reference-matrix.md
+  - skills/references/rule-loading-map.md
+  - skills/references/flow-test-cases.md
+  - skills/references/prompt-replay-checklist.md
+  - skills/references/full-chain-replay-scenarios.md
+---
+
+# Workflow Router
+
+## Purpose
+
+Route a request to the right stage and skill. This skill ends when the next skill is selected.
+
+## Suitable / Unsuitable
+
+- Suitable: stage selection, handoff, intent disambiguation
+- Unsuitable: requirement analysis, design, implementation, review, capture
+
+## Workflow
+
+1. Identify the intent type.
+2. Select the next stage and skill.
+3. Attach the needed inputs.
+4. Hand off to the target skill.
+
+## Replay Signals
+
+- Input signal: user intent, current stage, or available artifacts.
+- Output to verify: next skill, stage decision, handoff note.
+- Stop signal: any target-skill work or rule loading.
+- Handoff signal: the next skill is selected and ready.
+
+## Examples
+
+- Input: "We need a new feature but the stage is unclear."
+- Output: selected next skill and handoff note
+- Stop: do not start analysis or implementation
+
+- Input: "Just tell me which step comes next."
+- Output: next skill decision and minimal handoff note
+- Stop: do not begin the target work
+
+## Stop Rules
+
+- Stop after routing.
+- Do not perform the target skill's work.
+- Do not perform the next skill's work.
+- Do not add rule details.
+
+## References
+
+- `skills/references/skill-reference-matrix.md`
+- `skills/references/rule-loading-map.md`
+- `skills/references/flow-test-cases.md`
+- `skills/references/prompt-replay-checklist.md`
+- `skills/references/full-chain-replay-scenarios.md`