kf-architect

To translate feature requests into structured implementation plans, provide your prompt to the architect. It researches your codebase to generate self-contained track specifications with clear scopes and dependencies.

Splitting cross-cutting feature work into backend and frontend tracks is handled through coordinated BE/FE thinking. The architect divides large requests and merges track artifacts back to the primary branch for worker claim.

Managing dependency analysis and pre-flight checks for new feature tracks is automated by the architect. It enforces pre-flight context loading and strict merge protocols to prevent conflicts before developers claim work.

Branch conflicts during track merging occur without a strict merge protocol. The architect enforces pre-flight dependency analysis and coordinated merging to the primary branch to prevent these conflicts.

You can use this architect skill to generate ready-to-work tracks for any codebase. It requires no dependencies and researches your existing code structure to distill ambiguous requests into scoped track specifications.