product-development

Generate implementation specification documents from a product plan for iOS/macOS apps.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/mazicimert/RunDom --skill product-development-mazicimert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-development
Source: https://github.com/mazicimert/RunDom/tree/main/.claude/skills/product
Command: npx skills add https://github.com/mazicimert/RunDom --skill product-development-mazicimert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams struggle to transform abstract ideas into concrete, actionable development plans and consistent documentation across PRD, architecture, UX, and release specs.

Core Features & Use Cases

  • End-to-end specification generation from a product development plan, covering PRD, architecture, UX, implementation, test, and release docs.
  • Phase-based orchestration with review gates to ensure alignment before proceeding.
  • Outputs ready-to-use artifacts saved to docs/ (PRD.md, ARCHITECTURE.md, UX_SPEC.md, DESIGN_SYSTEM.md, IMPLEMENTATION_GUIDE.md, TEST_SPEC.md, RELEASE_SPEC.md).
  • Use cases: MVP scoping, architecture reviews, QA readiness, and release planning.

Quick Start

Submit your product plan and run the orchestration to generate all docs.

Frequently Asked Questions about product-development

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

FAQPage Schema
How do I generate implementation specifications from a product plan?

Implementation specifications are generated by submitting a product plan to orchestrate phase-based generation, producing ready-to-use artifacts like PRD.md, ARCHITECTURE.md, and IMPLEMENTATION_GUIDE.md saved to the docs directory.

What documents are needed for iOS and macOS app product development?

iOS and macOS app product development requires comprehensive documentation including PRD, architecture, UX spec, design system, implementation guide, test spec, and release spec to ensure alignment across teams.

Can I automate PRD and architecture doc creation for an MVP scope?

PRD and architecture doc creation is automated for MVP scoping by applying end-to-end specification generation with review gates to ensure alignment before proceeding to development.

Does the product specification workflow integrate with product-agent outputs?

The product specification workflow satisfies integration with product-agent outputs, taking the generated product plan as input to orchestrate the downstream creation of UX, testing, and release docs.

What is the best way to structure release planning and QA readiness docs?

Release planning and QA readiness docs are structured by generating standardized TEST_SPEC.md and RELEASE_SPEC.md files, ensuring consistent testing and deployment tracking across the product lifecycle.