بنقرة واحدة
scaffold-design-spec
Create template stub files for newly enabled catalog entries, including user-facing documentation
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Create template stub files for newly enabled catalog entries, including user-facing documentation
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Whole-repo, multi-agent audit that IS the Sprint-end cross-review ceremony (product-wide integrity): 4 axes — spec-conformance, logic/defect hunt, redundancy, and product-security — over the ACCUMULATED codebase at HEAD, not the Sprint diff. Findings are swept to zero per defect class — one class = one PBI covering every occurrence, documentation drift batched into a single DOCS PBI — and non-blocking: Critical/High become draft PBIs for the NEXT Sprint, Medium/Low at PO discretion. At Integration-Sprint entry a thin re-check confirms the latest audit is fresh and no open Critical/High audit PBIs remain before testing proceeds.
Sprint-end product-wide integrity gate. The five per-aspect reviews (requirement conformance, functional quality, security, maintainability, docs consistency) now run PER-PBI inside the pipeline before a PBI reaches awaiting_cross_review. Sprint-end cross-review is the whole-repo codebase-audit ONLY: static analysis + 4 audit axes (spec-conformance, logic-defect, redundancy, product-security) over the accumulated codebase at HEAD. The audit is non-blocking — Critical/High findings become draft PBIs for the next Sprint; it never reverts a PBI.
Handles PBI pipeline escalation notifications from Developer. Reads escalation context, applies response matrix (retry / split / hold / human), and routes to user when human intervention is needed.
SM-side merge orchestration for a single PBI. Triggered when the Developer notifies `[<pbi-id>] PBI_READY_TO_MERGE`. Drives `.scrum/scripts/merge-pbi.sh` and handles the failure / retry cycle through SendMessage to the assigned Developer.
PBI development pipeline — orchestrates design, impl+UT, PBI review, and UT-run stages with sub-agent fan-out, file-based handoff, and deterministic termination gates (Anthropic + Ralph + GAN-derived). Used by Developer per assigned PBI. Replaces former design + implementation skills.
PO acceptance verification — launches and operates the app to verify acceptance criteria by command execution. Used in Sprint Review (demo mode) and Integration Sprint (UAT mode) when .scrum/config.json po_mode is "agent".
| name | scaffold-design-spec |
| description | Create template stub files for newly enabled catalog entries, including user-facing documentation |
| disable-model-invocation | false |
docs/design/catalog.md (doc type reference)docs/design/catalog-config.json (enabled spec IDs)sprint.json → idbacklog.json → PBI IDs for related_pbisdocs/design/specs/{category}/{id}-{slug}.md stub filesdocs/design/specs/{category}/{id}-{slug}.md (auto-create dirs)
b. YAML frontmatter: catalog_id, created_sprint, last_updated_sprint (same), related_pbis, frozen: false, revision_history (initial entry: sprint, author: "scrum-master", date, summary: "Initial stub created", pbis)
c. Placeholder sections: Overview, Design Details, Constraints, References
d. Category docs/→doc placeholders: Overview, Usage, API Reference, Examples
e. Category technology/→library-spec placeholders: Library & Version,
Verified API Surface, Gotchas, Sources (source URL per claim)D-001 (one file per decision), S-022 (one per external service), and
S-070 (one per third-party library) are multi-instance. Scaffold the single
name-slug base stub as for any enabled ID; additional instances are created
on demand by their owning agent — e.g. pbi-designer writes
technology/S-070-<lib-slug>.md per library during the Design stage. All files
sharing an enabled ID's prefix satisfy Governance Rules 1–2 (keyed on spec ID,
not exact slug); do not delete extra instances as "non-enabled".
Ref: FR-004
This skill only writes stubs to the working tree. The caller
(sprint-planning Step 13) MUST commit docs/design/ to main before
spawn-teammates runs freeze-sprint-base.sh — worktrees fork from
committed HEAD, so an uncommitted stub reaches no PBI worktree.
freeze-sprint-base.sh refuses while docs/design/ is dirty.