write-wp-design

Generate a structured design.md for a work-package from a domain backlog and template.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/daddia/space --skill write-wp-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-wp-design
Source: https://github.com/daddia/space/tree/main/.agents/skills/write-wp-design
Command: npx skills add https://github.com/daddia/space --skill write-wp-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams produce consistent, sprint-level design documentation by translating backlog and domain context into structured work-package design guides.

Core Features & Use Cases

  • Generates walking-skeleton or TDD design.md templates based on the parent domain backlog/solution.
  • References parent patterns and keeps governance aligned with domain-wide templates.
  • Produces a ready-to-save work/{d}/{wp}/design.md with sections, file lists, and acceptance gates.

Quick Start

Provide the domain, epic title, and work-package identifiers and ask the skill to generate the design document at the expected path.

Frequently Asked Questions about write-wp-design

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

FAQPage Schema
How do I generate a work-package design document from a domain backlog?

To generate a work-package design document, provide the domain, epic title, and work-package identifiers to interpret the domain backlog and solution. It produces a structured design.md with sections for scope, architecture fit, data contracts, and testing strategy.

What is a walking-skeleton template for sprint-level design?

A walking-skeleton template is a structured design approach that generates a design.md outlining scope, architecture fit, files, components, and runtime view for a work-package. It references the parent domain backlog and solution inline to align sprint execution with governance.

Can I use TDD design templates for documenting work-package architecture?

Yes, you can generate a TDD design template for documenting work-package architecture. The output design.md includes sections for testing strategy, acceptance gates, data contracts, and open questions, placing the document at the expected work package path.

What sections are included in an automated work-package design.md?

An automated work-package design.md includes sections for scope, architecture fit, files and components, data contracts, runtime view, testing strategy, acceptance gates, handoff, and open questions. It references the parent domain backlog and solution inline for context.

How do I keep sprint-level design documentation aligned with domain-wide patterns?

To keep sprint-level design documentation aligned with domain-wide patterns, the generated design.md references the parent domain backlog and solution inline. This ensures the work-package scope, architecture fit, and data contracts maintain governance with domain templates.