Produce a TypeScript architectural specification from discovery findings.
npx skills add https://github.com/kagenti/humr --skill spec-kagenti
Please help me install this Agent Skill. Skill: spec Source: https://github.com/kagenti/humr/tree/main/.agents/skills/spec Command: npx skills add https://github.com/kagenti/humr --skill spec-kagenti
This Skill helps teams conduct thorough discovery and produce high-level architectural specifications that align with the project's TypeScript engineering approach, capturing domain concerns, bounded contexts, and service boundaries without prescribing concrete implementations.
Ask aligned discovery questions and request a high-level architectural spec for a new feature.
High-intent search queries and answers about installing and using this skill.
To create an architectural specification, conduct guided discovery interviews to elicit domain boundaries and event flows, then map those bounded contexts to your TypeScript architecture. This identifies affected modules, integration points, and layer responsibilities to guide implementation without prescribing concrete code.
Identifying bounded contexts and domain events requires structured discovery. By mapping domain concerns and event flows through guided interviews, you can clearly define service boundaries, affected modules, and integration points to ensure architectural alignment and minimize rework.
Yes, you can map domain concerns to integration points without implementation code. This process produces an implementation-agnostic, architecture-focused specification that defines layer responsibilities and collaboration patterns, deliberately avoiding concrete code prescriptions.
Guided discovery helps define service boundaries by using structured interviews to elicit domain responsibilities and event flows. It maps these bounded contexts directly to your TypeScript architecture, ensuring clear separation of concerns and identifying necessary integration points.
You need a high-level architectural specification when capturing domain boundaries and event flows is critical before coding. It guides implementation by identifying affected modules and collaboration patterns early, minimizing rework and ensuring architectural alignment across your TypeScript project.
harshilLakhani22Map domain concepts, terminology conflicts, and bounded contexts.
liminal-aiTransform feature specifications into tech design documents with architecture and test mapping.
buddypiaGenerates strategic domain models with DDD and Event Storming Lite from briefs.
VSF-QC-TTSStandardize architecture diagrams using C4 and UML models with Mermaid syntax.
