Required Resources
Always load before running:
- •
references/routing.md - •
references/enhancement_checklist.md - •
references/definition_of_done.md - •
references/validation.md - •
assets/templates/enhancement_template.md - •Optional calibration example:
assets/examples/enhancement_example_torus-1234.md
Workflow
- •Parse inputs: ticket key (
<jira-key>), request text, and optional feature slug override. - •Resolve destination using
references/routing.md. - •Create/update enhancement doc from template:
- •Feature-pack mode:
docs/features/<feature_slug>/enhancements/<jira-key>.md - •Mini-pack mode:
docs/work/<jira-key>/enhancement.md
- •Feature-pack mode:
- •Fill required sections with concise, testable content from
references/enhancement_checklist.md. - •Run enhancement-doc validation hard gate from
references/validation.md. - •If in feature-pack mode, run full spec-pack validation hard gate from
references/validation.md. - •Route implementation:
- •Feature-pack mode: run
spec_designfor the enhancement slice, then runspec_developfor implementation. - •Mini-pack mode: perform design+develop inline using this skill's checklist, because
spec_designandspec_developare feature-pack scoped.
- •Feature-pack mode: run
- •Re-run validation gates after doc updates caused by implementation.
Validation Gate
- •Always run:
- •
python3 .agents/skills/spec_enhancement/scripts/validate_enhancement_doc.py <enhancement_doc_path>
- •
- •Additionally, in feature-pack mode run:
- •
.agents/scripts/spec_validate.sh --slug <feature_slug> --check all
- •
- •If any validation fails, fix docs and re-run before proceeding.
- •Execute commands directly when environment access allows; do not merely suggest them.
Output Contract
- •Create/update exactly one enhancement doc for the ticket.
- •Report destination mode (
feature-packormini-pack), key ACs, implementation status, tests run, and validation status. - •If routing confidence is low, state why mini-pack mode was selected.