structure

Map approved designs to files, interfaces, and architectural diagrams.

36|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/dfrysinger/qrspi-plus --skill structure-dfrysinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: structure
Source: https://github.com/dfrysinger/qrspi-plus/tree/main/skills/structure
Command: npx skills add https://github.com/dfrysinger/qrspi-plus --skill structure-dfrysinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate an approved design into a deterministic, file-level implementation plan so teams can move from abstract architecture to concrete code changes with clear boundaries and responsibilities.

Core Features & Use Cases

  • File and Slice Mapping: Maps design vertical slices to specific files and components with explicit create vs modify actions.
  • Interface Definitions: Produces function/class signatures and interface boundaries to prevent integration mismatches.
  • Reviewable Artifact Workflow: Generates structure.md, runs review rounds (Claude and optional Codex), records review findings, and gates progression until human approval.
  • Use Case: When design.md is approved for a new feature or quick fix, produce structure.md to define files, interfaces, and CI needs before planning and implementation.

Quick Start

Use the structure skill to generate structure.md that maps design.md slices to files, states create or modify for each file, and defines interfaces and an architectural diagram for review.

Frequently Asked Questions about structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map an approved software design to concrete files and interface definitions?

To map an approved design to concrete files and interface definitions, generate a structure.md document that translates design vertical slices into specific file-level create or modify actions, typed signatures, and a Mermaid architectural diagram.

What is the best way to translate abstract architecture into a file-level implementation plan?

Translating abstract architecture into a file-level implementation plan involves mapping design.md vertical slices to specific components, defining explicit interface boundaries to prevent integration mismatches, and producing create or modify actions for each file.

How does artifact gating work when generating a file-level implementation plan?

Artifact gating enforces progression by requiring approved goals.md, research/summary.md, and design.md documents before generating structure.md, ensuring design validation occurs before file mapping and interface contract definition.

Can I define typed interfaces and component boundaries before writing code?

Yes, you can define typed interfaces and component boundaries before writing code by generating a structure document that establishes function and class signatures, preventing integration mismatches during the implementation phase.

Does the structure workflow support review rounds and human approval gating?

The structure workflow supports review rounds and human approval gating by generating structure.md, running automated review checks, recording findings, and requiring explicit human approval before proceeding to code implementation.

When do I need to generate a structure document with file maps and architectural diagrams?

You need to generate a structure document with file maps and architectural diagrams when design.md is approved for new features, quick fixes, or greenfield projects requiring explicit file-level actions and interface contracts before implementation.