Generate a per-story high-level design with contract-gated integration decisions.
npx skills add https://github.com/gleeb/ai-registry --skill planning-hld
Please help me install this Agent Skill. Skill: planning-hld Source: https://github.com/gleeb/ai-registry/tree/main/systems/sdlc/skills/planning-hld Command: npx skills add https://github.com/gleeb/ai-registry --skill planning-hld
It produces a per-story high-level design (HLD) that keeps architecture consistent, prevents contract drift, and ensures each user story’s scope and integrations are explicitly traceable.
Use the planning-hld skill to generate the HLD for story US-NNN-name by ensuring story.md, plan/system-architecture.md, consumed contracts in plan/contracts/, and the relevant plan/prd.md sections are present for context.
High-intent search queries and answers about installing and using this skill.
A per-story high-level design scoped to a single user story defines component responsibilities, data flows, and integration points while enforcing REQUIRE/DENY gates against consumed contracts to prevent interface drift.
Before creating a contract-safe high-level design, ensure story.md, plan/system-architecture.md, plan/prd.md, and consumed contracts in plan/contracts/ are present to provide the required context for Phase 3 HLD generation.
Integration realization during per-story HLD design selects mock, interface-only, real, or realize modes by reading consumed contracts, ensuring shared interfaces are utilized without redefinition under REQUIRE/DENY gate enforcement.
Yes, per-story high-level design maps design units directly to user story acceptance criteria using the HLD template, producing a review-ready structure that ensures explicit traceability for sparring review.
The correct output artifact for a user story high-level design document is written to plan/user-stories/US-NNN-name/hld.md, using the standardized HLD template with explicit integration realization decisions.
You should not use a per-story HLD approach when system-architecture.md or consumed contracts are missing, as the REQUIRE/DENY gates require these inputs to validate integration points and prevent contract drift.
cosmixGenerate OpenAPI-based API documentation covering endpoints, schemas, authentication, and errors.
ryan-nguyen-01Generate a structured High-Level Design document covering architecture, deployment, security, and integration points.
BellaBeSynthesize opposing positions into a structured thesis-antithesis-synthesis artifact.
jaisonerickGenerate end-to-end QA spec files and an index mapping tests to validation criteria.
