joycraft-design

Generate a five-section design document from a feature brief.

14|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/maksutovic/joycraft --skill joycraft-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: joycraft-design
Source: https://github.com/maksutovic/joycraft/tree/main/.agents/skills/joycraft-design
Command: npx skills add https://github.com/maksutovic/joycraft --skill joycraft-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams catch wrong assumptions early by producing a focused design artifact before decomposition, reducing rework and clarifying scope.

Core Features & Use Cases

  • Generates a ~200-line design document bridging research and decomposition.
  • Creates docs/designs/YYYY-MM-DD-feature-name.md with a standardized five-section structure.
  • Provides guardrails and a clear handoff point to decomposition.

Quick Start

Provide a feature brief or path and I will generate the design document for review.

Frequently Asked Questions about joycraft-design

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

FAQPage Schema
How do I draft a design discussion document before feature decomposition?

To draft a design discussion document before feature decomposition, provide a feature brief to generate a structured markdown file that validates intent, clarifies scope, and establishes clear handoff guardrails.

What should a feature design document include to catch wrong assumptions early?

A feature design document should include Current State, Desired End State, Patterns to Follow, Resolved Design Decisions, and Open Questions to catch wrong assumptions early and reduce rework before decomposition.

How do I structure a design doc to bridge research and feature decomposition?

You structure a design doc to bridge research and decomposition by generating a standardized five-section markdown artifact that provides guardrails and a clear handoff point for downstream development.

Do I need a feature brief to generate a design document?

Yes, you need an existing feature brief or research input path to generate the design document, which serves as the starting point for exploring decisions and creating the artifact in the docs directory.

Where should I save design specs in my repository for team review?

You should save design specs as markdown files formatted like docs/designs/YYYY-MM-DD-feature-name.md, ensuring the feature design documentation is standardized and accessible for team review.

What is the best way to validate feature intent before starting decomposition?

The best way to validate feature intent before decomposition is producing a focused 200-line design artifact that explores decisions and resolves open questions, reducing rework by clarifying scope early.