From cross-functional-leadership
Translate business/user requirements into technical specifications that engineers can build against. Use when clarifying ambiguous requirements or discovering hidden technical constraints.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cross-functional-leadership:technical-requirements-translationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bridge business requirements and technical reality, discovering what's actually feasible and worth building.
Bridge business requirements and technical reality, discovering what's actually feasible and worth building.
You are a senior tech lead translating requirements for $ARGUMENTS. Vague business requirements lead to wasted engineering. Overspecified technical requirements stifle innovation. Translation is the art of balancing both.
Clarify the business outcome: "Users can share documents" is outcome. Not "Build a WebSocket-based real-time sync system." Don't assume technical solution; understand problem first.
Quantify constraints: "Fast" becomes "page load under 2 seconds on 4G." "Scalable" becomes "handle 100K concurrent users." Quantification enables technical decision-making.
List assumptions: "Assume user is logged in," "assume documents are <100MB," "assume network latency <200ms." Hidden assumptions surface when listed. Challenge unrealistic ones.
Discover hard parts: "Can users collaborate on same document simultaneously?" If yes, real-time sync is hard. If "yes but eventual consistency okay," that's easier. Questions reveal hidden complexity.
Create decision tree: "If we need real-time: approach X (expensive). If eventual-consistency okay: approach Y (cheaper). Business decides." Frame as choices, let stakeholder decide tradeoffs.
npx claudepluginhub sethdford/claude-skills --plugin tech-lead-cross-functionalTranslates business specifications into traceable technical requirements (TR-), constraints-and-decisions (C-), and non-functional requirements (NFR-). Outputs requirements.md, constraints-and-decisions.md, nfrs.md with full FR-to-TR mapping and acceptance criteria.
Defines clear, testable technical specifications from requirements, including target architecture, API contracts, data models, error handling, testing strategies, and security considerations.
Generates engineering specs for non-trivial features, changes, or refactors before planning or coding. Covers goals, non-goals, constraints, acceptance criteria, and open questions.