jp-plan

To create datestamped planning phase directories, use a dedicated command to generate a .plans/YYYY/MM/DD/NN-<slug> folder structure. This automatically creates nested reviews and cycle folders, initializes a prompt.md template, and sets up state.yaml with active branch tracking.

Automating project planning phase management involves generating sequentially numbered, datestamped directories within a .plans folder. This workflow derives a filename-friendly slug from your description, creates a prompt.md skeleton, and initializes state.yaml for status tracking.

Yes, this planning workflow integrates with Git by recording the active branch for each phase. It initializes a state.yaml file during directory creation to track the branch and current status, ensuring your planning phases align with your version control strategy.

The generated prompt.md template includes sections for Overview, Goals, Requirements, Constraints, Out of Scope, and References. This skeleton provides a standardized structure to document the objectives and boundaries of each planning phase.

To initialize a new planning phase from a text description, run the plan command followed by your description. The system generates a concise slug from the text, creates the datestamped phase directory, and populates it with a prompt.md template and state.yaml file.

You need a Git-based project utilizing a .plans directory structure. The automation creates nested YYYY/MM/DD/NN-<slug> phase folders containing reviews and cycle subfolders, requiring no additional dependencies to generate the phase directories and tracking files.