Converts confirmed Change Request items into standardized 10-section specification documents.
npx skills add https://github.com/Angel1104/architecture-docs --skill spec-angel1104
Please help me install this Agent Skill. Skill: spec Source: https://github.com/Angel1104/architecture-docs/tree/main/FE-MOBILE/commands/spec Command: npx skills add https://github.com/Angel1104/architecture-docs --skill spec-angel1104
The Spec Skill provides a disciplined, repeatable workflow to translate a Change Request (CR) item into a comprehensive, approved specification. It ensures alignment between intake, scope, and implementation by enforcing a standardized 10-section template and explicit gating rules.
Start by confirming a CR item with /intake and then begin drafting its spec using the standard template and the CR context.
High-intent search queries and answers about installing and using this skill.
A change request specification needs a standardized 10-section template covering context, scope, and acceptance criteria. It enforces gated phases from context loading to handoff, adjusting depth by CR size and risk to ensure cross-team alignment.
A gated phase workflow for documentation enforces sequential stages: context loading, proportionality calibration, drafting, multi-agent review, and handoff. This structured process ensures formal validation and cross-team alignment before proceeding to implementation.
When drafting a spec and missing business decisions are detected, validation guardrails flag the omissions and prompt for the missing acceptance criteria. This ensures formal documentation is complete before cross-team handoff.
Yes, a single 10-section specification template applies to both bug fixes and feature changes. The workflow uses proportionality calibration to adjust documentation depth appropriately based on the specific CR size and risk level.
The best way to structure cross-team alignment for a change request is using a multi-agent review workflow within a standardized template. This enforces clear acceptance criteria and tracks status through gated phases to ensure complete formal documentation.
Angel1104Automate engineering change request lifecycle from intake to close.
LeoCode03Generates CR specification documents with domain, architecture, security analysis.
tense-iOrchestrate adversarial code reviews with opposing-model reviewers and synthesized verdicts.
NSEvteevCreate standardized 10-section service documentation files at specs/docs/{svc}.md.
