itinerary-builder

To build a custom itinerary with POI map pins and AI recommendations, the skill executes tasks phase by phase from a master planner document, enforcing strict phase ordering and binding decisions via a decision log to prevent chaotic project delivery.

Phase management prevents scope creep by parking out-of-scope requests into a scope-creep registry instead of silently expanding the build, while only executing the next unchecked task for the currently active phase to maintain strict ordering.

The best way to maintain a decision log for private-tour itinerary building is enforcing binding decisions through a master planner document, recording all choices, and updating the log with last commit hash, phase status, and checklist progress after each commit.

No, using this itinerary builder for a tour recommendation engine requires a full read-through of a master planner document at docs/itinerary-builder-plan.md to drive next unchecked task execution, binding decision compliance, and mandatory planner updates.

To update the master planner after completing itinerary tasks, the skill automatically synchronizes operational data including last commit hash, phase status, change log entries, and checklist progress to ensure the build state remains consistently tracked.

An itinerary builder skips phases during product planning if strict phase ordering is not enforced; this skill prevents that by executing only the next checklist task for the currently active phase and requiring mandatory planner updates after each commit.