End-to-end project planning toolkit: converts requirements into structured phased implementation plans, groups phases into dependency-ordered waves for parallel subagent execution, and decomposes large branches into focused pull requests.
90
90%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
#!/usr/bin/env sh
# Usage: new-phase.sh <plan-slug> <phase-number> <phase-slug>
# Creates: .context/plans/plan-<plan-slug>/phases/phase-<NN>-<phase-slug>/README.md
set -eu
PLAN_SLUG="${1:?Usage: new-phase.sh <plan-slug> <phase-number> <phase-slug>}"
PHASE_NUM="${2:?Usage: new-phase.sh <plan-slug> <phase-number> <phase-slug>}"
PHASE_SLUG="${3:?Usage: new-phase.sh <plan-slug> <phase-number> <phase-slug>}"
PHASE_DIR=".context/plans/plan-${PLAN_SLUG}/phases/phase-$(printf '%02d' "${PHASE_NUM}")-${PHASE_SLUG}"
mkdir -p "${PHASE_DIR}/tasks"
cat > "${PHASE_DIR}/README.md" <<EOF
# Phase $(printf '%02d' "${PHASE_NUM}") — ${PHASE_SLUG}
## Goal
<!-- One or two sentences: what this phase delivers and why it is a natural milestone. -->
## Gate
<!-- Checklist of binary, runnable acceptance criteria. -->
- [ ] <!-- \`command\` exits 0 -->
## Dependencies
<!-- Bullet list of prior phases, files, services, or ADRs this phase depends on. -->
## Tasks
<!-- One H3 per task. Add rows as tasks are created. -->
EOF
echo "Created ${PHASE_DIR}/README.md"