sdlc-biz-to-tech

Translate business requirements into a Technical Requirements Document grounded in the codebase.

1|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/OlixIgnacious/agent-skills --skill sdlc-biz-to-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-biz-to-tech
Source: https://github.com/OlixIgnacious/agent-skills/tree/main/.claude/skills/sdlc-biz-to-tech
Command: npx skills add https://github.com/OlixIgnacious/agent-skills --skill sdlc-biz-to-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps translate business requirements into a Technical Requirements Document (TRD), bridging the gap between business goals and technical implementation.

Core Features & Use Cases

  • Business to Technical Translation: Converts business requirements, PRDs, stakeholder asks, or vague goals into a Technical Requirements Document (TRD).
  • Parallel Orchestration: Delegates tasks to the biz-to-tech-orchestrator, which spawns requirements-analyst and code-archaeologist in parallel.
  • Grounded Implementation: Produces a TRD that is grounded in the actual codebase and ready for architectural review.

Quick Start

Generate a Technical Requirements Document for a feature request by providing the business input and executing the skill.

Frequently Asked Questions about sdlc-biz-to-tech

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

FAQPage Schema
How do I translate business requirements into a technical requirements document?

The TRD bridges business goals and technical implementation by converting business requirements, PRDs, and stakeholder asks into precise technical specifications grounded in the actual codebase.

How to generate a technical requirements document from a PRD?

You can generate a technical requirements document from a PRD by passing the business input to a translation process that spawns requirements analysis and code archaeology tasks in parallel to ground the output.

What is the best way to convert stakeholder asks into technical specifications?

The best way to convert stakeholder asks into technical specifications is using a parallel orchestration approach that simultaneously analyzes requirements and examines the existing codebase to produce an architecture-ready TRD.

Does business to technical translation work with an existing codebase?

Yes, business to technical translation works with an existing codebase by delegating tasks to a code archaeologist that grounds the generated technical requirements document in the actual source code and architectural structure.

Can I use a technical requirements document for architectural review?

Yes, you can use a technical requirements document for architectural review because the translation process produces a TRD that is grounded in the actual codebase and ready for architectural evaluation.