How does this skill differ from writing business requirements?

While business requirements focus on user goals, this skill focuses on the technical capabilities, constraints, and system-level behaviors required to fulfill those goals.

Can I use this for implementation planning?

This skill is intended for the requirement definition phase. Once these technical requirements are established, you should use separate planning skills for implementation tasks.

What are the five artifacts produced by this skill?

It generates Technical Requirements (TR), Technical Constraints (C), Non-Functional Requirements (NFR), System Integrations (INT), and Data Sensitivity (DS) classifications.

Why are integrations mapped with failure modes?

To ensure system resilience, the skill mandates documenting what happens when external dependencies fail, preventing the common mistake of designing for optimistic 'happy paths' only.

Technical Requirements Authoring

Name: Technical Requirements Authoring
Author: deepeshBodh

bydeepeshBodh

•

Collaboration Tools

Translates business specifications into measurable, traceable technical artifacts including requirements, constraints, and integration maps.

This skill transforms high-level business goals into a rigorous technical foundation by generating five distinct, interconnected artifacts. It ensures every technical requirement traces back to a business source while enforcing measurable non-functional targets, explicit failure modes for integrations, and mandatory data sensitivity classifications. Ideal for teams practicing a spec-first development approach, it acts as a quality gate that prevents architectural gaps and ensures security-by-design before implementation begins.

Key Features

01Automated decomposition of business requirements into granular technical TR-XXX entries.

02Comprehensive system integration mapping including protocol details, failure modes, and fallback strategies.

0324 GitHub stars

04Mandatory data sensitivity classification and retention policy mapping for every data element.

05Measurable Non-Functional Requirement (NFR) definition with specific numeric targets and verification methods.

06Full traceability matrix ensuring every technical artifact connects to a verified business source.

Use Cases

01Documenting external API dependencies and their associated failure behaviors before implementation.

02Translating a business PRD into developer-ready technical specifications and acceptance criteria.

03Establishing a security and compliance baseline through data sensitivity and encryption mapping.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add deepeshbodh/human-in-loop authoring-technical-requirements

For use in Claude.ai and ChatGPT

Download Skill