architect

Convert a PM Plan and repository context into a DESIGN.md document.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/PanJason/Awesome_SDE_Skills --skill architect-panjason
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/PanJason/Awesome_SDE_Skills/tree/main/Architect
Command: npx skills add https://github.com/PanJason/Awesome_SDE_Skills --skill architect-panjason

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a PM Plan (PLAN.md) and project context into a concrete Technical Design Document (DESIGN.md) that describes system architecture and implementation approach.

Core Features & Use Cases

  • Transform PM plans into a comprehensive DESIGN.md containing components, data models, API contracts, and system diagrams.
  • Leverage existing repository context to tailor architecture decisions and task assignments for frontend, backend, and DevOps teams.
  • Provide a clear handoff artifact for engineering sprints and QA validation.

Quick Start

Provide PLAN.md and repository context to the design generator, and it will output DESIGN.md.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I turn a PM plan into a technical design document?

To turn a PM plan into a technical design document, provide the PLAN.md and repository context to generate a formal DESIGN.md specifying components, data models, interfaces, and developer tasks.

What is included in a system design document for engineering handoff?

A system design document for engineering handoff includes system architecture, data models, API contracts, data flow, and step-by-step developer tasks tailored for frontend, backend, and DevOps implementation.

How to generate API contracts and data models from a product plan?

Generate API contracts and data models from a product plan by processing the PM plan alongside existing repository context to produce a formal DESIGN.md that outlines schema definitions and interface specifications.

Does the technical design generation work with existing repository context?

Yes, technical design generation leverages existing repository context to tailor architecture decisions and specific task assignments for frontend, backend, and DevOps teams within the output DESIGN.md.

Can I use this for planning frontend, backend, and DevOps implementation tasks?

Yes, you can use this to plan frontend, backend, and DevOps implementation tasks, as the generated DESIGN.md provides step-by-step developer tasks and clear handoff artifacts for engineering sprints.

What is the best way to structure a DESIGN.md for engineering sprints?

The best way to structure a DESIGN.md for engineering sprints is to define system architecture, data flow, and API contracts, providing a clear handoff artifact for implementation teams and QA validation.