skills.rest
wtah
wtahCOMMUNITY
Explore all skills by this author →
GitHub

technical-constraints

Standardize technology, infrastructure, and integration constraints in .constraints/ files.

Updated Feb 6, 2026
Search Tags:#architecture#governance#infrastructure#constraints#integrations#technology-stack#standardize
One-click install
npx skills add https://github.com/wtah/spec-master --skill technical-constraints
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-constraints
Source: https://github.com/wtah/spec-master/tree/main/.claude/skills/technical-constraints
Command: npx skills add https://github.com/wtah/spec-master --skill technical-constraints

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized structure for capturing and enforcing architectural constraints, including technology stack, infrastructure, and integrations, serving as input for architecture decisions. Located in the .constraints/ directory.

Core Features & Use Cases

  • Centralizes Technology, Infrastructure, and Integrations constraints in a single, reusable blueprint.
  • Guides architecture decisions by providing hard boundaries and rationales for design choices.
  • Use Case: At project kickoff, create TECHNOLOGY.md, INFRASTRUCTURE.md, and INTEGRATIONS.md inside .constraints/ to bound technology choices, hosting, and external system interactions.

Quick Start

Create a .constraints/ directory at the project root and populate TECHNOLOGY.md, INFRASTRUCTURE.md, and INTEGRATIONS.md with constrained requirements and rationales.

Frequently Asked Questions about technical-constraints

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

FAQPage Schema
How do I document architecture constraints for technology stack and infrastructure?▼

To document architecture constraints, create a .constraints/ directory at your project root and populate TECHNOLOGY.md, INFRASTRUCTURE.md, and INTEGRATIONS.md with bounded requirements and rationales to guide system design.

What are technical constraints in early-stage system design?▼

Technical constraints are standardized hard boundaries for technology choices, infrastructure requirements, and integration interactions that serve as required inputs for making architecture decisions across programs.

How do I standardize integration boundaries and technology choices at project kickoff?▼

You standardize integration boundaries by creating three markdown files under .constraints/ that define approved technology stacks, hosting requirements, and external system interactions, including stated rationales for each boundary.

Can I use this constraint model for programs outside of software engineering?▼

The constraint model applies to early-stage system design across programs, specifically guiding software architecture decisions regarding technology, infrastructure, and integrations rather than non-technical program management.

Best way to enforce infrastructure requirements and integration limits during architecture decisions?▼

The best way to enforce infrastructure and integration limits is to centralize them in a reusable .constraints/ blueprint, providing hard boundaries and rationales that directly guide and restrict architecture choices.

Why do I need rationale included in technical constraints files?▼

Rationale is needed in technical constraints files to guide architecture decisions by providing the reasoning behind hard boundaries, ensuring design choices respect the original technology, infrastructure, and integration limits.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
krzysztofsurdykrzysztofsurdy
20

architect

Guide software architecture design and document technical decisions with ADRs.

Community
Advanced
pythoninthegrassespythoninthegrasses
1

architecture-decision-records

Document architectural decision context, options, and rationale in standardized ADR format.

Official
Advanced
johannesfritzjohannesfritz
1

write-adr

Create MADR-compliant Architecture Decision Records and update the ADR index.

Community
Intermediate