Converts PRD requirements into modules, APIs, data models, and non-functional decisions.
npx skills add https://github.com/lync-cyber/CataForge --skill arc-design
Please help me install this Agent Skill. Skill: arc-design Source: https://github.com/lync-cyber/CataForge/tree/main/.cataforge/skills/arc-design Command: npx skills add https://github.com/lync-cyber/CataForge --skill arc-design
This Skill helps turn approved product requirements into a coherent system architecture, so teams can move from what to build into how to structure it.
Use the arc-design skill to design a full architecture for the provided PRD and return modules, interfaces, data models, non-functional decisions, and directory structure.
High-intent search queries and answers about installing and using this skill.
System architecture from a PRD is designed by translating product requirements into modules, API contracts, data models, and non-functional decisions. It selects an appropriate architectural style based on project constraints and defines implementation-ready directory structures for downstream development teams.
A technical architecture specification includes module breakdowns, API contracts, and data models derived from product requirements. It also defines non-functional architecture, configuration strategy, and directory structures to guide downstream implementation teams.
Breaking PRD functionality into modules and API contracts involves mapping product requirements to architectural components. This process defines clear interface contracts and data models, ensuring the resulting structure is implementation-ready for development teams.
Yes, this architecture design approach works for CLI systems and broader software products. It applies to product-to-engineering handoff and technical planning scenarios by defining non-functional decisions, configuration strategies, and directory structures.
The best way to plan configuration strategy and directory structure is during operational planning after selecting an architectural style. This defines development conventions and non-functional architecture to ensure implementation-ready structure for downstream engineering teams.
jaimedhenriquesGenerate product requirements documents with user stories and acceptance criteria.
ilandahanGenerate a technical specification from PRDs and requirements.
Alfie728Draft a complete engineering PRD from an approved arch-brief.
ilandahanGuide Tech Lead teams through architecture decisions and code review criteria.
