Translate non-technical PRDs into architecture decisions and a Build Plan.
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill prd-intake
Please help me install this Agent Skill. Skill: prd-intake Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.squad/skills/prd-intake Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill prd-intake
Architects often struggle to convert non-technical PRDs and feature requests into concrete, technically sound plans. This skill provides a disciplined intake process that translates user needs into architecture-aligned decisions and a clear Build Plan.
Provide a concise PRD description to begin translating into a Build Plan for Architect.
High-intent search queries and answers about installing and using this skill.
To convert non-technical PRDs into actionable architecture decisions, you can use a structured intake process that asks 3-5 targeted questions to extract goals, constraints, and success criteria from informal inputs, mapping them directly to technical build plans.
Translating stakeholder feature requests into a formal build plan involves enforcing a validation flow that extracts desired outcomes, clarifies scope without overburdening the user, and produces architecture notes alongside acceptance criteria for approval.
Yes, you can apply this intake process to informal ideas across teams. It is designed to handle onboarding briefs and stakeholder requests by guiding conversations to reveal critical gaps and translate non-technical user needs into architecture-aligned decisions.
The intake flow asks 3-5 targeted questions to validate PRD completeness. This guides conversations to reveal critical gaps and clarify scope, ensuring informal inputs are fully translated into technical decisions and a structured build plan.
Translating a PRD generates a structured build plan document that outlines architecture choices, acceptance criteria, and next steps for approval. It also produces architecture notes to align technical decisions with the extracted goals.
epicsagasTranslate complex project details into plain language for non-technical audiences.
xhyqaqConvert approved product specifications into structured acceptance criteria with pass/fail checks.
LazyIsEfficientDraft technical strategy documents with diagnosis, policy, actions, and kill criteria.
DengNaichenGenerate dependency-ordered development tasks from specification and planning documents.
