Decomposes large engineering tasks into estimated sub-tickets aligned with existing architecture.
npx skills add https://github.com/mitchellfyi/dex --skill dxrefine
Please help me install this Agent Skill. Skill: dxrefine Source: https://github.com/mitchellfyi/dex/tree/main/skills/dxrefine Command: npx skills add https://github.com/mitchellfyi/dex --skill dxrefine
This Skill eliminates the ambiguity and risk of tackling large, unstructured engineering tasks by providing a structured, architecture-aligned refinement process that clarifies scope, identifies risks, and breaks work into actionable, estimated sub-tickets before any implementation begins.
Use the dxrefine skill to refine your engineering task description into a structured plan with estimated, shippable sub-tickets aligned to your project's architecture.
High-intent search queries and answers about installing and using this skill.
To break down large engineering tasks into estimated sub-tickets, you refine unstructured work into independently shippable units aligned with your project's existing architecture. This process maps work to components, identifies risks, and assigns clear domain ownership.
Architecture-aligned scoping is a refinement process mapping unstructured engineering tasks to your project's existing C4 architecture. It identifies impacted components, flags documentation drift, and surfaces applicable design patterns before implementation begins.
You identify cross-component risks and edge cases by applying a structured technical refinement process to feature work and system changes. This surfaces non-functional requirements and potential drift early, reducing rework during implementation.
You need design pattern surfacing when decomposing complex features or bug fixes requiring cross-component alignment. It identifies applicable design patterns for each sub-ticket, reusing existing codebase patterns to avoid unnecessary reinvention.
Yes, you can use this technical refinement approach for feature work, bug fixes, and system changes. It decomposes any large, unstructured engineering task into scoped sub-tickets that respect project constraints and assign clear domain ownership.
The best way to scope engineering plans respecting project constraints is to decompose tasks into estimated, independently shippable sub-tickets. This method clarifies scope, surfaces edge cases, and aligns work with your current architecture documentation.
BridgingIT-GmbHConvert descriptive text into Mermaid class, sequence, flowchart, ERD, and C4 diagrams.
MatrixFounderOrchestrate parallel execution of decomposed tasks by spawning asynchronous sub-agents.
Busboom-FooEvaluate sprint architecture updates for consistency with the baseline system.
DangQuangSEAutomate sprint planning, task breakdowns, and story point estimation.
