feat: project context panel (PROJECT.md / STATE.md context engineering) #188

New Issue

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

hikari commented

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

Overview

Inspired by get-shit-done (GSD)'s context engineering approach, this adds a Project Context Panel — a dedicated UI for creating and managing structured persistent context files that Claude always has access to across sessions.

The Problem: Context Rot

As Claude's context window fills up, response quality degrades. GSD solves this by maintaining a set of persistent state files that ground Claude in the project's purpose, requirements, and current state — regardless of how many tokens have been consumed.

Feature Details

Managed Files

The panel manages the following files in the project root:

File	Purpose
`PROJECT.md`	Vision and goals — always loaded into Claude's context
`REQUIREMENTS.md`	Scoped requirements with phase traceability
`ROADMAP.md`	Progress tracking and milestone planning
`STATE.md`	Current decisions, blockers, and position (cross-session memory)

Panel UI

File tabs across the top (PROJECT / REQUIREMENTS / ROADMAP / STATE)
Rich markdown editor for each file with live preview
Template button — populate each file with a sensible starting template
"Inject into next prompt" toggle — prepend the selected file's contents into the next Claude message
Auto-load setting — optionally auto-prepend PROJECT.md to every new conversation
Status indicator — shows which files exist vs. need to be created

Project Initialisation Wizard

A one-time flow for new projects:

"What are you building?" — populates PROJECT.md vision
"What must be in v1?" — populates REQUIREMENTS.md
"What's your tech stack?" — adds constraints to PROJECT.md
Generates ROADMAP.md with suggested milestones

STATE.md Auto-Update

After each successful conversation (when Claude completes a task), optionally append a timestamped summary to STATE.md:

What was done
What decisions were made
What blockers remain
Current position in the roadmap

This ensures cross-session continuity without manual upkeep.

Integration with Task Loop

When the Task Loop (see #183) runs tasks, it can automatically inject the relevant context files at the start of each task's conversation.

Acceptance Criteria

Panel displays and allows editing of PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md
Project initialisation wizard creates all four files from user input
Files can be injected into the next Claude prompt manually
Auto-load setting prepends PROJECT.md to every new conversation
After task completion, STATE.md can be optionally updated with a summary
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 **context engineering** approach, this adds a **Project Context Panel** — a dedicated UI for creating and managing structured persistent context files that Claude always has access to across sessions. ## The Problem: Context Rot As Claude's context window fills up, response quality degrades. GSD solves this by maintaining a set of persistent state files that ground Claude in the project's purpose, requirements, and current state — regardless of how many tokens have been consumed. ## Feature Details ### Managed Files The panel manages the following files in the project root: | File | Purpose | |------|---------| | `PROJECT.md` | Vision and goals — always loaded into Claude's context | | `REQUIREMENTS.md` | Scoped requirements with phase traceability | | `ROADMAP.md` | Progress tracking and milestone planning | | `STATE.md` | Current decisions, blockers, and position (cross-session memory) | ### Panel UI - **File tabs** across the top (PROJECT / REQUIREMENTS / ROADMAP / STATE) - **Rich markdown editor** for each file with live preview - **Template button** — populate each file with a sensible starting template - **"Inject into next prompt" toggle** — prepend the selected file's contents into the next Claude message - **Auto-load setting** — optionally auto-prepend PROJECT.md to every new conversation - **Status indicator** — shows which files exist vs. need to be created ### Project Initialisation Wizard A one-time flow for new projects: 1. "What are you building?" — populates PROJECT.md vision 2. "What must be in v1?" — populates REQUIREMENTS.md 3. "What's your tech stack?" — adds constraints to PROJECT.md 4. Generates ROADMAP.md with suggested milestones ### STATE.md Auto-Update After each successful conversation (when Claude completes a task), optionally append a timestamped summary to STATE.md: - What was done - What decisions were made - What blockers remain - Current position in the roadmap This ensures cross-session continuity without manual upkeep. ### Integration with Task Loop When the Task Loop (see #183) runs tasks, it can automatically inject the relevant context files at the start of each task's conversation. ## Acceptance Criteria - [ ] Panel displays and allows editing of PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md - [ ] Project initialisation wizard creates all four files from user input - [ ] Files can be injected into the next Claude prompt manually - [ ] Auto-load setting prepends PROJECT.md to every new conversation - [ ] After task completion, STATE.md can be optionally updated with a summary - [ ] Tests written for all new logic ✨ This issue was created with help from Hikari~ 🌸

hikari referenced this issue

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

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

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 this issue

2026-03-06 09:39:06 -08:00

feat: auto-commit after task completion in task loop #192

hikari referenced this issue from a commit

2026-03-06 12:13:41 -08:00

feat: project context panel for persistent PROJECT/REQUIREMENTS/ROADMAP/STATE files (#188)