gathering-architecture-requirements
Planning skill. Use before building anything to gather requirements through structured discovery questions. Covers dimensions, UX, data, governance, and planning cycles. Load this skill during Phase 0 of building-a-full-application.
Install
With your agent
Install OMGSkills skill "gopigment/ai-plugins:skills/gathering-architecture-requirements" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/gopigment/ai-plugins /tmp/ai-plugins && ln -s /tmp/ai-plugins/skills/gathering-architecture-requirements ~/.claude/skills/gathering-architecture-requirementsFrom README
Gathering Architecture Requirements Work through each area systematically, gathering requirements and making decisions before proceeding to the spec. --- Dimensions and Structure At what granularity will users input data for each business dimension? At what granularity will calculations occur? Do dimension item mappings change over time (employee moving cost centers)? What level drives user access rights? Are there organizational hierarchies with varying granularity needs? Which dimensions are required in the structure? Can any be replaced with properties or mapped dimensions? --- End User UX Can you provide wireframes or mockups of desired input screens? Can you share examples of current reports before Pigment? On which dimensions do users need to input? What are the key final reports (P&L, etc.)? What variations need to appear as columns in reports? What KPIs or ratios are required, and how are they calculated? Do certain calculations require separate metrics vs calculated items?