feat: guided project workflow (Discuss → Plan → Execute → Verify phases) #189

New Issue

2026-03-06T09:38:23-08:00

hikari commented

2026-03-06 09:38:23 -08:00

Overview

Inspired by get-shit-done (GSD)'s four-phase workflow, this adds a Guided Project Workflow panel — a structured approach to feature development that walks through Discuss, Plan, Execute, and Verify phases, each with dedicated prompts and output capture.

The Problem: Vibe Coding

Jumping straight into asking Claude to "implement X" leads to wasted context on misunderstandings, missed edge cases, and poor architecture decisions. GSD's insight is that structured phases dramatically improve output quality.

Feature Details

The Four Phases

Phase 1: Discuss

User describes what they want to build
Claude identifies gray areas, ambiguities, and decisions that need to be made before coding
Output: CONTEXT.md capturing all decisions and constraints
UI: Guided Q&A conversation tab, "Capture to CONTEXT.md" button

Phase 2: Plan

Claude (optionally spawning parallel research agents) creates a structured task plan
Plan is presented as editable task cards (integrates with PRD Creator, see #184)
Verification loop: a second Claude pass checks the plan meets requirements
Output: hikari-tasks.json task list with dependency metadata
UI: Plan display with approve/edit/regenerate controls

Phase 3: Execute

Runs the approved task plan through the Task Loop (see #183)
Supports wave-based execution respecting task dependencies
Each task gets a fresh conversation context
Output: Completed code changes, per-task SUMMARY.md files
UI: Task Loop panel with progress visualisation

Phase 4: Verify

Extracts testable deliverables from the plan
Claude walks through acceptance testing
Auto-diagnoses failures and creates fix plans
Output: Verification report
UI: Checklist of acceptance criteria with pass/fail status

Workflow Panel UI

Phase stepper at the top showing current position (1→2→3→4)
Each phase has its own sub-panel with relevant controls
Phases can be skipped or revisited
Overall project progress tracked in ROADMAP.md
"Quick mode" toggle to skip optional steps (research, verification) for ad-hoc tasks

Phase State Persistence

Current phase and progress saved to STATE.md
Resumable across app restarts
Phase history viewable (what was decided in Discuss, what was planned, etc.)

Integration Points

Uses Project Context Panel (#188) for STATE.md updates
Uses PRD Creator (#184) for the Plan phase task generation
Uses Task Loop (#183) for the Execute phase
Each completed phase updates ROADMAP.md automatically

Acceptance Criteria

Four-phase workflow panel with phase stepper UI
Discuss phase captures decisions to CONTEXT.md
Plan phase generates and displays task plan with approve/edit controls
Execute phase runs the task loop and shows progress
Verify phase presents acceptance criteria with pass/fail tracking
Phases can be skipped or revisited
Phase state persists across app restarts
Quick mode available to skip optional steps
Tests written for all new logic

✨ This issue was created with help from Hikari~ 🌸

## Overview Inspired by [get-shit-done (GSD)](https://github.com/gsd-build/get-shit-done)'s four-phase workflow, this adds a **Guided Project Workflow** panel — a structured approach to feature development that walks through Discuss, Plan, Execute, and Verify phases, each with dedicated prompts and output capture. ## The Problem: Vibe Coding Jumping straight into asking Claude to "implement X" leads to wasted context on misunderstandings, missed edge cases, and poor architecture decisions. GSD's insight is that structured phases dramatically improve output quality. ## Feature Details ### The Four Phases **Phase 1: Discuss** - User describes what they want to build - Claude identifies gray areas, ambiguities, and decisions that need to be made before coding - Output: CONTEXT.md capturing all decisions and constraints - UI: Guided Q&A conversation tab, "Capture to CONTEXT.md" button **Phase 2: Plan** - Claude (optionally spawning parallel research agents) creates a structured task plan - Plan is presented as editable task cards (integrates with PRD Creator, see #184) - Verification loop: a second Claude pass checks the plan meets requirements - Output: `hikari-tasks.json` task list with dependency metadata - UI: Plan display with approve/edit/regenerate controls **Phase 3: Execute** - Runs the approved task plan through the Task Loop (see #183) - Supports wave-based execution respecting task dependencies - Each task gets a fresh conversation context - Output: Completed code changes, per-task SUMMARY.md files - UI: Task Loop panel with progress visualisation **Phase 4: Verify** - Extracts testable deliverables from the plan - Claude walks through acceptance testing - Auto-diagnoses failures and creates fix plans - Output: Verification report - UI: Checklist of acceptance criteria with pass/fail status ### Workflow Panel UI - **Phase stepper** at the top showing current position (1→2→3→4) - Each phase has its own sub-panel with relevant controls - Phases can be skipped or revisited - Overall project progress tracked in ROADMAP.md - "Quick mode" toggle to skip optional steps (research, verification) for ad-hoc tasks ### Phase State Persistence - Current phase and progress saved to STATE.md - Resumable across app restarts - Phase history viewable (what was decided in Discuss, what was planned, etc.) ### Integration Points - Uses Project Context Panel (#188) for STATE.md updates - Uses PRD Creator (#184) for the Plan phase task generation - Uses Task Loop (#183) for the Execute phase - Each completed phase updates ROADMAP.md automatically ## Acceptance Criteria - [ ] Four-phase workflow panel with phase stepper UI - [ ] Discuss phase captures decisions to CONTEXT.md - [ ] Plan phase generates and displays task plan with approve/edit controls - [ ] Execute phase runs the task loop and shows progress - [ ] Verify phase presents acceptance criteria with pass/fail tracking - [ ] Phases can be skipped or revisited - [ ] Phase state persists across app restarts - [ ] Quick mode available to skip optional steps - [ ] Tests written for all new logic ✨ This issue was created with help from Hikari~ 🌸

hikari referenced this issue

2026-03-06 09:38:37 -08:00

feat: codebase mapper (auto-generate architectural summary for Claude's context) #190

hikari referenced a pull request that will close this issue

2026-03-07 02:12:27 -08:00

feat: productivity suite — task loop, workflow, theming, docs & more #197

naomi closed this issue

2026-03-07 03:08:33 -08:00

naomi referenced this issue from a commit

2026-03-07 03:08:34 -08:00

feat: productivity suite — task loop, workflow, theming, docs & more (#197)

Sign in to join this conversation.