technical-design

Produces repository-grounded technical design proposals covering modules, interfaces, seams, and migration strategies.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/ahsanghalib/ai-workflow --skill technical-design-ahsanghalib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-design
Source: https://github.com/ahsanghalib/ai-workflow/tree/main/skills/technical-design
Command: npx skills add https://github.com/ahsanghalib/ai-workflow --skill technical-design-ahsanghalib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents premature or ungrounded implementation by producing an evidence-based technical design proposal before any code is written, clearly separating observed repository facts from assumptions. ## Core Features & Use Cases - Repository-Grounded Design: Inspects code, tests, configuration, and history to ground proposals in real constraints while never reading secrets or credentials. - Module and Contract Specification: Defines public interfaces, dependency strategies, failure modes, observability, and compatibility for each proposed module. - Alternatives and Validation Planning: Compares materially different designs for consequential decisions and defines approval-gated validation steps. - Use Case: Before adding a new payment integration, use this Skill to analyze the existing codebase, propose module boundaries and test seams, compare two adapter strategies, and produce a design brief for approval. ## Quick Start Ask the assistant to propose a technical design for your planned change, grounded in the current repository, without editing any files.

Frequently Asked Questions about technical-design

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

FAQPage Schema
How do I create a technical design document before implementing a feature?▼

Use this Skill to inspect the repository, frame the problem and constraints, propose modules and contracts, and compare alternatives. It returns a structured design brief covering evidence, seams, trade-offs, migration, and validation strategy.

How to compare architecture alternatives for a codebase change?▼

The Skill compares two or three materially different designs for consequential decisions, evaluating interface shape, seam placement, coupling, operational risk, and migration cost. It recommends one option and lists unresolved questions.

When should I not use a technical design workflow?▼

Do not use it for product discovery, founder-level prioritization, general repository inventory, delivery planning, or direct implementation. Those tasks belong to companion skills like product-discovery, repository-research, or project-init.

Does the technical design skill edit code or run tests?▼

No. It never edits files, runs generators, migrations, tests, or network calls without explicit approval. It stops at an approved proposal and hands implementation off to a separate workflow.

Can the design proposal read environment files or credentials?▼

No. The Skill explicitly forbids reading or reproducing .env files, credentials, secret stores, tokens, or keys. It grounds proposals only in code, tests, configuration structure, documentation, and history.