microsoft / microsoft/hve-core
refactor(skills): progressive disclosure for release-readiness-gate (references + templates)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 301
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 92
Description
## Summary
Follow-up from the #2422 review (F4, @katriendg). Apply progressive disclosure to the `release-readiness-gate` skill so `SKILL.md` stays compact, per the prompt-builder guidance.
## Proposed changes
- Move the **Default Pillars** table to `references/pillars.md`, loaded on demand.
- Move the **scorecard template** (Output Format) to `templates/scorecard.md`.
- Reference both from `SKILL.md` instead of inlining them.
## Context
- Deferred from #2422 to keep that PR focused on collection placement (F1) and section structure (F3).
- Severity: Low.
## Acceptance criteria
- `SKILL.md` references `references/pillars.md` and `templates/scorecard.md` instead of inlining that material.
- `npm run validate:skills` and `npm run lint:frontmatter` pass.
- Plugins regenerated via `npm run plugin:generate`.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the release-readiness-gate SKILL.md and identify the inlined Default Pillars table and scorecard template. Move them to references/pillars.md and templates/scorecard.md, update the references, then run npm run validate:skills, npm run lint:frontmatter, and npm run plugin:generate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 84/100