dev-spec-driven

Manage iOS feature development through spec, design, and task artifacts.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/nguyennamkkb/ios-spec-driven --skill dev-spec-driven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-spec-driven
Source: https://github.com/nguyennamkkb/ios-spec-driven/tree/main/src/ios_spec_driven_installer/templates/.claude/skills/dev-spec-driven
Command: npx skills add https://github.com/nguyennamkkb/ios-spec-driven --skill dev-spec-driven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, end-to-end spec-driven workflow for iOS development, enabling teams to capture requirements, design, and task plans in a structured, traceable manner.

Core Features & Use Cases

  • Feature-based workflow: Create requirements, design, and tasks as distinct artifacts to enforce stage gates.
  • Traceability: Link user stories, acceptance criteria, design decisions, and tasks to maintain a full audit trail.
  • Guided automation: Stepwise agent-driven execution (write-spec, write-design, write-tasks, execute-tasks) to guide from idea to code.
  • Use Case: For a new iOS feature, generate a requirements.md, design.md, and tasks.md, then implement with automated checks and checkpoints.

Quick Start

Initiate a new feature by creating requirements, then design, then tasks, followed by executing tasks.

Frequently Asked Questions about dev-spec-driven

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

FAQPage Schema
How do I manage iOS feature development from requirements to code execution?

iOS feature development is managed using a spec-driven workflow that enforces stage gates through distinct artifacts: requirements.md, design.md, and tasks.md. A stepwise agent chain guides the process from initial idea to code execution with automated checkpoints.

What is spec-driven workflow and how does it ensure traceability for new features?

Spec-driven workflow captures requirements, design decisions, and tasks as structured artifacts to maintain a full audit trail. It links user stories, acceptance criteria, and tasks to ensure traceability throughout the feature development lifecycle.

Can I use this spec-driven workflow for existing iOS projects or is it only for new features?

This spec-driven workflow is suitable for new feature rollouts within iOS engineering projects. It guides teams from the initial concept through requirements, design, and task execution to maintain structured traceability.

How do I generate design and task documents for an iOS feature rollout?

Design and task documents are generated through a guided agent chain: write-spec, write-design, write-tasks, and execute-tasks. This stepwise automation creates design.md and tasks.md artifacts sequentially with user confirmations at each checkpoint.

Does this workflow integrate with standard iOS engineering tools and frameworks?

The workflow applies to iOS engineering projects by enforcing artifacts like requirements.md, design.md, and tasks.md. It operates through an agent-driven chain to guide implementation, suitable for teams needing structured feature traceability.

What are the limitations of using a spec-driven workflow for iOS development?

The spec-driven workflow requires user confirmations at each stage gate, meaning it enforces a strict stepwise process from write-spec to execute-tasks. It is designed specifically for iOS engineering projects and new feature rollouts.