Route technical decisions into design paths with Socratic Inquiry and Gate 4 acceptance.
npx skills add https://github.com/Sheldon-92/TAD --skill alex
Please help me install this Agent Skill. Skill: alex Source: https://github.com/Sheldon-92/TAD/tree/main/.agents/skills/alex Command: npx skills add https://github.com/Sheldon-92/TAD --skill alex
This self-contained Skill acts as a TAD Solution Lead, orchestrating requirement clarification, architecture planning, and multi-module handoffs with gate-keeping at critical points to ensure human-in-the-loop decisions and artifact traceability.
Describe a complex feature and enter *analyze to begin a Socratic Inquiry-driven design and handoff workflow.
High-intent search queries and answers about installing and using this skill.
Complex design handoffs require orchestrating requirement clarification through Socratic Inquiry rounds and capability pack loading. This ensures technical decisions are routed into appropriate design paths while maintaining artifact traceability and updating Epic and Phase flows.
Socratic Inquiry in architecture planning is a multi-round questioning process to clarify complex requirements before design execution. It is needed when identifying technical decisions and routing tasks into appropriate design paths for multi-module handoffs.
Gate 4 business acceptance is managed by ensuring deliverables are documented and Epic and Phase flows are updated. Cross-project governance keeps NEXT.md, PROJECT_CONTEXT.md, and Epics in sync during handoff creation and capability pack validation.
A Solution Lead workflow supports multi-module architecture planning by performing grounding passes, frontmatter validation, and capability pack loading. It tailors design rules and ensures human-in-the-loop decisions during critical gate-keeping points.
To start a design orchestration workflow, describe a complex feature and trigger the analysis phase. This initiates a Socratic Inquiry-driven design and handoff workflow that identifies technical decisions and performs grounding passes.
Cross-project governance requires keeping NEXT.md and PROJECT_CONTEXT.md in sync to maintain knowledge alignment across modules. This ensures artifact traceability and proper Epic and Phase tracking during Gate 4 business acceptance and handoff creation.
hongliangcAutomate updates to project_context.md after major codebase changes.
lucaswallConvert Linear backlog issues into structured test-driven implementation plans.
GarethManningDesign structured awe moments that connect lesson content to inquiry.
KaranKathur06Transform ambiguous ideas into an approved, sectioned design spec.
