Sequence the build
sequence_buildRead-onlyIdempotent
Turn a feature list with dependencies into a dated build plan: applies the MVP cut, orders tasks by dependency, schedules them across the given number of builders on working days (weekends skipped), computes the critical path and each task's slack, adds the method's own tasks (record the success metric, take payment, launch kit, Hand Off) where missing, and dates the milestones: first core job end to end, MVP in real users' hands, launch, success metric review, and Hand Off. Every plan carries a success metric and a review date; a default per product type is used and flagged when none is given.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | "mvp": must-haves only. "launch" (default): must-haves plus should-haves that fit the window. "all": everything. | |
| builders | No | People building in parallel. Default 1. | |
| features | Yes | ||
| start_date | No | ISO date the build starts. Default today (UTC). Weekends are skipped. | |
| build_weeks | No | Build window in weeks. Default 6. | |
| product_type | No | Used for the default success metric when none is given. | |
| success_metric | No | The number that decides success, its target, and how many days after launch to read it. | |
| points_per_week | No | Effort points one builder clears in a week. Default 5. | |
| charge_at_launch | No | True if buyers pay from launch. Default true. | |
| validate_first_days | No | Working days of validation before the build starts. Default 0. | |
| include_method_tasks | No | Add the method's own tasks: metric recording, payment, launch kit and Hand Off. Default true. |