god-agent-plan

To plan architecture and specs for a codebase, you can use a structured workflow that integrates research, interviews, and external reviews to generate comprehensive artifacts. This process enforces a standardized pipeline to produce self-contained docs for traceability.

Coordinating UI and backend planning boundaries is best handled by a multi-phase workflow that analyzes input to synthesize specs, architecture, and implementation plans. It surfaces integration notes across design-system and codebase considerations to ensure alignment.

Generating traceable implementation plans from an initial brief involves running a guided command that validates input, drives research decisions, and synthesizes specs. This outputs self-contained documents under designated directories for execution and traceability.

Yes, you can use guided prompts and subagents to conduct automated interviews that gather insights and validate decisions for software architecture. This collaborative approach ensures design and codebase considerations are thoroughly evaluated before artifact generation.

No specific dependencies are required to run this multi-phase project planning workflow. The skill operates independently to orchestrate research, interviews, and external reviews, producing standardized architecture and spec artifacts directly in your project directories.

You should avoid using a structured artifact pipeline for project planning when your project scope is too small to require formal specs, architecture documentation, or multi-phase interviews, as the overhead of generating traceable docs outweighs the benefits.