compose

Synthesize module documentation into business-layer Use Case and User Story drafts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill bridges the gap between isolated technical module documentation and the user-facing business narrative, ensuring that cross-module flows are coherent and well-defined.

Core Features & Use Cases

  • Cross-Module Synthesis: Automatically maps technical module entry points into a unified business-layer Use Case and User Story.
  • Failure Analysis: Conducts a structured interview to define cross-module error handling and edge-case behaviors.
  • Use Case: When you have completed technical documentation for an auth module and a payment module, use this skill to generate the business-layer checkout flow that connects them.

Quick Start

Use the compose skill to create a business-layer use case by combining the auth and payment modules.

Frequently Asked Questions about compose

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

FAQPage Schema
How do I generate user stories from existing technical module documentation?

To generate user stories from technical module documentation, the compose skill synthesizes confirmed module-level docs into comprehensive business-layer Use Case and User Story drafts, bridging the gap between isolated technical modules and user-facing narratives.

What is the best way to map cross-module user journeys and handle failure scenarios?

Mapping cross-module user journeys and failure scenarios is handled through a structured three-phase interview process that defines actor goals, cross-module error handling, and edge-case behaviors to ensure coherent cross-module flows.

Can I use this to document a checkout flow connecting auth and payment modules?

Yes, you can use this skill to document a checkout flow connecting auth and payment modules by synthesizing their confirmed technical documentation into a unified business-layer Use Case that maps the cross-module user journey.

How does cross-module synthesis maintain implementation layer tracking for use cases?

Cross-module synthesis maintains implementation layer tracking for use cases by automatically mapping technical module entry points into a unified business-layer narrative while preserving strict implementation layer mapping and coverage tracking.

When do I need to synthesize business-layer use cases from isolated technical docs?

You need to synthesize business-layer use cases from isolated technical docs when you have completed module-level documentation for separate components and must generate coherent, project-layer documentation that connects cross-module user flows.

Are there limitations to automating user story generation from technical documentation?

Automating user story generation from technical documentation requires confirmed module-level technical documentation as input; it cannot synthesize business-layer use cases from incomplete or unverified module architecture and implementation details.