Generate a technical liaison plan from product requirements and prototypes.
npx skills add https://github.com/konglong87/superPM --skill pm-tech
Please help me install this Agent Skill. Skill: pm-tech Source: https://github.com/konglong87/superPM/tree/main/skills/02-solution-design/pm-tech Command: npx skills add https://github.com/konglong87/superPM --skill pm-tech
pm-tech helps product and technical stakeholders convert product requirements into a concrete, feasible technical approach by aligning scope, architecture, interfaces, and third-party options before engineering commits.
Use case example: you have a product PRD and prototype draft, and the team needs an evidence-based plan covering architecture, feasibility, core APIs (RESTful), and third-party integrations so development can start with clear assumptions.
Use pm-tech to generate a technical liaison plan by providing your PRD (or MVP) and prototype documents, then answer the requested technical scope options.
High-intent search queries and answers about installing and using this skill.
To convert a PRD into a technical plan, the tool extracts key requirements, drafts architecture, designs RESTful APIs, and evaluates third-party services. It uses an interactive scope selection process to align technical boundaries before generating a structured technical liaison document.
Assessing technical feasibility requires evaluating implementation difficulty per feature and identifying high-risk items based on PRD inputs. The tool performs evidence-based feature difficulty analysis and estimates third-party service needs to ensure engineering readiness.
Yes, generating an architecture design requires both PRD and prototype documents as inputs. The tool checks for these missing inputs during a pre-check guidance phase and prompts you to provide them to ensure accurate technical scope alignment.
Yes, you can evaluate third-party service costs during API design. The tool integrates engineering risk and cost readiness by estimating third-party service needs and identifying cost drivers alongside drafting the core interface specifications.
Technical scope alignment works by using AskUserQuestion-driven selection to clarify whether you need an overall solution, feasibility assessment, or API design. This ensures the drafted architecture and interface planning match your specific product-to-engineering handoff requirements.
anipatkeCreate structured product requirement documents from user inputs and notes.
konglong87Convert product requirements into a prototype design plan document.
hekinamiDesign OpenAPI 3.0 API specifications from user stories and architecture documents.
zerAdaEvaluate technical feasibility of architecture options and implementation approaches.
