design-plan

Translate business-layer documentation into module contracts and implementation plans.

Updated May 6, 2026
One-click install
npx skills add https://github.com/SuSuSleep/scaffold --skill design-plan-sususleep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-plan
Source: https://github.com/SuSuSleep/scaffold/tree/main/skills/design-plan
Command: npx skills add https://github.com/SuSuSleep/scaffold --skill design-plan-sususleep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between high-level business requirements and technical implementation by generating structured module-layer contracts and sequenced work plans.

Core Features & Use Cases

  • Module Contract Generation: Automatically derives module-specific use cases and user stories from business-layer drafts.
  • Implementation Sequencing: Creates batched work items with clear dependency mapping and affected file tracking.
  • Use Case: After a business feature is approved, use this skill to break down the implementation into specific module tasks, proposed file changes, and integration verification steps.

Quick Start

Run the design-plan skill to generate the implementation plan and module contracts for the current business-layer drafts.

Frequently Asked Questions about design-plan

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

FAQPage Schema
How do I translate business requirements into technical implementation plans?

To translate business requirements into technical implementation plans, this skill processes business-layer documentation to generate structured module-layer contracts, ADRs, and batched task lists with clear dependency mapping.

What is the best way to generate module contracts from business documentation?

Generating module contracts from business documentation involves deriving module-specific use cases and user stories from approved business drafts to establish technical specifications for implementation.

How do I create batched work items with dependency mapping for software architecture?

Creating batched work items with dependency mapping involves sequencing implementation tasks from project-level documentation scaffolds, tracking affected files, and defining integration verification steps.

Do I need specific schema versions to generate architectural documentation?

Yes, generating architectural documentation requires strict adherence to project-specific schema versions and naming conventions to ensure consistent architectural output and accurate module contracts.

Can I use this approach to bridge high-level business drafts and technical scaffolding?

Yes, this approach bridges high-level business drafts and technical scaffolding by operating on project-level documentation to derive module contracts and actionable plans, closing the gap between requirements and code.

When should I not use automated implementation sequencing for project planning?

Avoid automated implementation sequencing when lacking approved business-layer drafts or project-specific schema versions, as the tool requires existing scaffolds to accurately derive module contracts and track dependencies.