_workflow-spec

Generate structured markdown specification documents from user-provided requirements.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Piece-Puzzly/Piece-iOS --skill workflow-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _workflow-spec
Source: https://github.com/Piece-Puzzly/Piece-iOS/tree/main/.claude/skills/_workflow-spec
Command: npx skills add https://github.com/Piece-Puzzly/Piece-iOS --skill workflow-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed specification documents based on user-provided requirements, streamlining the product development process.

Core Features & Use Cases

  • Requirement Gathering: Guides users to provide comprehensive details for features.
  • Spec Document Generation: Creates structured spec.md files with sections for overview, requirements, UI, API, edge cases, and testing.
  • Use Case: A product manager needs to document a new feature. They describe the feature to the AI, provide a Figma link, and the AI generates a complete spec.md file ready for review.

Quick Start

Describe the feature you want to implement, including any Figma or API links, and then say "작성해줘".

Frequently Asked Questions about _workflow-spec

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

FAQPage Schema
How do I generate a spec document for a new software feature?

You can generate a spec document by describing your feature requirements, UI specifications, and API details. The system compiles this information into a structured markdown spec.md file, covering overview, edge cases, and acceptance criteria.

Can I use Figma links when creating requirements for spec generation?

Yes, you can use Figma links during spec generation. The system supports Figma context retrieval to help compile UI specifications and detailed requirements into your final markdown spec document.

What is the best way to document API details and edge cases for product management?

The best way to document API details and edge cases is using automated spec generation. It guides you through providing API specifics and acceptance criteria, compiling them into a structured spec.md file.

Do I need git to automate workflow documentation and spec generation?

Yes, git is required as a dependency to automate workflow documentation and spec generation. The system uses git to manage the creation and versioning of your structured markdown specification files.

What sections are included in an automated spec.md file?

An automated spec.md file includes sections for overview, requirements, UI specifications, API details, edge cases, and testing acceptance criteria, providing a comprehensive software feature specification.