architecture-skill

Map PRD and story-map artifacts to a traceable system architecture package.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Galharel/my-codex-skills --skill architecture-skill-galharel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-skill
Source: https://github.com/Galharel/my-codex-skills/tree/main/architecture-skill
Command: npx skills add https://github.com/Galharel/my-codex-skills --skill architecture-skill-galharel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate PRD and story map artifacts into a high-level system architecture brief that preserves traceability to FR/NFR and story IDs, surfaces uncertainties, and guides designer handoffs across frontend, backend, data, and agentic workstreams.

Core Features & Use Cases

  • Produce an architecture package that links PRD/story artifacts to FR/NFR IDs and handoff contracts.
  • Surface uncertainty with targeted questions and present up to three options with pros/cons.
  • Generate designer handoffs for frontend, backend, data, and agentic domains, with traceability mappings to source artifacts.

Quick Start

Provide a concise architecture brief by feeding PRD and story-map artifacts to the Architecture Skill.

Frequently Asked Questions about architecture-skill

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

FAQPage Schema
How do I translate a PRD and story map into a system architecture brief?

To generate an architecture brief, map your PRD and story-map artifacts to high-level system components. This process links functional and non-functional requirements to handoff contracts across frontend, backend, data, and agentic domains.

What is requirement traceability in system architecture planning?

Requirement traceability in architecture planning maps functional and non-functional requirement IDs directly to system design components and designer handoff contracts. This ensures every architectural decision links back to source artifacts.

How do I handle uncertainty and surface trade-offs during architecture design?

To handle uncertainty during architecture design, surface targeted questions and present up to three design options with pros and cons. This guides decisions across frontend, backend, data, and agentic workstreams.

Do I need specific input formats to generate an architecture packet?

Generating an architecture packet requires authoritative inputs at docs/prd.packet.json and docs/story-map.json. These specific file formats provide the functional and non-functional requirements needed for traceability.

What's the best way to create designer handoffs for multi-domain system architecture?

The best way to create designer handoffs is mapping PRD and story-map artifacts to domain-specific contracts. This generates traceable handoffs for frontend, backend, data, and agentic workstreams with clear requirement mappings.

What output formats does an architecture brief generator produce?

An architecture brief generator produces a human-readable brief at docs/architecture.brief.md and a machine-readable packet at docs/architecture.packet.json. Both outputs maintain full traceability to source artifacts.