feature-planner

Plan feature architecture by orchestrating domain modeling, UI design, dependency wiring, and test scaffolding through a five-phase task dependency graph pipeline that outputs a final feature plan document. This coordinates parallelizable phased tasks to reduce integration risk.

Coordinate domain modeling and SwiftUI UI design by running a phased task graph pipeline that aligns design decisions early. You can isolate specific phases using CLI options like --domain-only or --ui-only to focus the feature plan output.

Yes, you can skip test scaffolding by passing the --skip-tests CLI option when running the feature planner. This excludes the testing phase from the task graph pipeline and generates a feature plan focused solely on architecture and design.

You need a task dependency graph when creating new features or major enhancements that require coordinating multiple design roles. It reduces integration risk by aligning domain modeling, UI architecture, and dependency wiring through a parallelizable pipeline.

Yes, the feature planning pipeline supports parallel Phase 1 analysis tasks to speed up architecture planning. It uses a task dependency graph to parallelize initial analysis before coordinating subsequent domain, UI, and wiring phases.