implementation-guide_skill

Overview

This skill generates a detailed, actionable implementation guide that transforms PRD, architecture, and UX specs into a developer-ready roadmap. It produces a comprehensive IMPLEMENTATION_GUIDE.md with pseudo-code, project setup steps, file structure, and phase-by-phase development instructions. The guide is tailored for Swift, SwiftUI, SwiftData projects and targets modern iOS development workflows.

How this skill works

The skill reads PRD, ARCHITECTURE.md, UX_SPEC.md, and DESIGN_SYSTEM.md to extract features, data models, flows, screens, and design tokens. It then synthesizes those inputs into a structured document: quick start, project setup, folder layout, model and networking pseudo-code, implementation phases, and testing/CI suggestions. It produces ready-to-copy Swift pseudo-code, initializer patterns, and stepwise tasks so any iOS developer can implement the app consistently.

When to use it

• You have completed PRD, architecture, and UX specs and need a developer roadmap.
• Preparing an MVP development plan and sprint breakdown for iOS/macOS.
• Handing off product details to a development team or contractor.
• Onboarding new engineers to a project with concrete steps and code examples.
• Estimating timelines and file counts for planning and resourcing.

Best practices

• Keep guides tied to source specs: update IMPLEMENTATION_GUIDE.md when PRD or ARCHITECTURE changes.
• Prioritize native frameworks (SwiftUI, SwiftData) and minimize third-party dependencies.
• Break work into clear phases: Core infra, Feature MVPs, Polish, and QA.
• Provide pseudo-code and small, tested units before full feature integration.
• Include CI, testing, and linting early to prevent regressions.

Example use cases

• Convert a product requirements doc and architecture decisions into a week-by-week implementation plan.
• Create a new SwiftUI app skeleton with SwiftData models and example ViewModel patterns.
• Generate detailed model and API pseudo-code for backend syncing and Codable mappings.
• Produce a developer onboarding doc with file structure, setup commands, and test examples.
• Draft an implementation checklist for reviews and QA that maps to acceptance criteria.