gears-frontx

Invoke when the user intent is analyzing the impact of an upstream artifact change (PRD/ADR/DESIGN/DECOMPOSITION/FEATURE) on downstream artifacts and code.

Invoke when the user asks to decompose, break down, or author/revise a DECOMPOSITION — e.g. "decompose", "break into features", "create the feature list / plan", "order features and dependencies with coverage back to PRD/DESIGN". Thin preset binding the DECOMPOSITION artifact KIND, delegating authoring and review to the core cf-write-docs engine.

Invoke when the user asks to author, write, revise, generate, or record an ADR or architecture decision — e.g. "generate ADR", "record a decision", "document why we chose X", "capture context / options / decision / consequences". Thin preset binding the ADR artifact KIND, delegating authoring and review to the core cf-write-docs engine.

Invoke when the user asks to author, write, revise, generate, or produce a DESIGN or system/technical design — e.g. "generate DESIGN", "design the system", "define components / interfaces / architecture / boundaries". Thin preset binding the DESIGN artifact KIND, delegating authoring and review to the core cf-write-docs engine.

Invoke when the user asks to author, write, revise, generate, or spec a FEATURE — e.g. "generate FEATURE", "spec the feature", "define flows / algorithms / states / definition of done (CDSL)", "write test scenarios for a feature". Thin preset binding the FEATURE artifact KIND, delegating authoring and review to the core cf-write-docs engine.

Invoke when the user asks to author, write, revise, or generate a PRD — e.g. "generate PRD", "write the PRD", "create product requirements", "capture actors, FR/NFR, use cases, or success criteria". Thin preset binding the PRD artifact KIND, delegating authoring and review to the core cf-write-docs engine.

Invoke when the user asks to implement, build, or write the code for a FEATURE — e.g. "implement", "write the code", "build this feature", "implement FEATURE with @cpt-* traceability". Thin preset binding the CODE artifact KIND, delegating implementation and review to the core cf-coding engine.

Invoke when the user intent is reconstructing SDLC artifacts (PRD/ADR/DESIGN/DECOMPOSITION/FEATURE) from existing code using code markers (@cpt-*) and the reverse-engineering methodology, without converting from another spec format.

FrontX ecosystem AI capabilities: MFE runtime substrate, GTS type system, API protocol surface, CLI scaffolding, and AI tooling kit. Routes a FrontX request to the capability that serves it. Solution-agnostic base only.

Applies when a developer wants a FrontX project built from what they say they want, rather than from a reference they already hold - for example a console with a stated number of screens - and equally when they want one more unit added to a project that already holds applied templates. Matches the stated intent against what the locally installed inventory declares about itself, drives the frontx executable to apply the chosen set, and then realizes each unit the intent names inside the applied ground.

Use this skill whenever delegating work to subagents — whether a single Task call or a full team via TeamCreate. Guides delegation, task decomposition, agent selection, and coordination. Covers when to spawn architect (design decisions, trade-offs), researcher (explorations, technical investigation), developer (FEATURE specs and code), tech-writer (documentation), qa (post-implementation validation), and architecture-critic (stress-testing architect output). Trigger on any subagent spawn, team creation, multi-agent coordination, or parallel work request.