Feature Plan: Project Chronicle Guard

1. Feature Name

Project Chronicle Guard

2. Reason

The user wants AI-human planning, questions, decisions, implementation details, bugs, and retrospectives to remain as project-specific Markdown knowledge instead of disappearing into chat history.

3. Original User Request

Add a Designer menu to the sidebar, similar in spirit to Team, and implement a staged Project Chronicle Guard system that records planning, decisions, development logs, bug fixes, and retrospectives.

4. Interpreted Intent

The user does not only want another chat prompt preset. They want a durable project knowledge layer that captures why decisions were made and keeps records separated by project.

5. Problems To Solve

Later readers forget why a direction was chosen.
AI questions lose their intent and decision impact.
Planning and implementation history are mixed or absent.
Multiple projects can contaminate each other's records.

6. MVP Scope

Add an independent projectChronicle module.
Add project profile types and Markdown writer utilities.
Add sidebar Designer controls for record project selection and basic project management.
Generate the project folder structure and seed Markdown files.
Save a planning document, discussion summary, decision record, development log, bug log, and timeline entry through explicit user actions.

7. Out Of Scope

Full automatic transcript recording
External database storage
Git auto-commit
Real-time file watching
Search UI
Tight integration with agent execution internals

8. Development Direction

Start with a low-risk independent module and connect the sidebar through message events. The chat agent can remain unaware of the record module in the first stage.

9. Existing Feature Relationship

The current sidebar already has Brain and Agent controls. The Designer menu should follow that UI pattern but manage project record profiles instead of agent skill files.

10. Dependency Strategy

Use TypeScript, Node fs, and Markdown files only. Store project profile metadata in VS Code global state and avoid modifying core chat execution.

11. Expected Value

Project-specific planning and decision history becomes reusable.
The user can intentionally create records before or after development work.
Future automation can build on a stable local file structure.

12. Success Criteria

A Designer selector appears in the sidebar.
A new record project can be created.
Record folders and seed files are generated safely.
Markdown documents can be generated without needing external services.
Existing chat, brain, and agent flows continue to compile.

13. Developer Instruction

Implement the first stage only: independent module, basic Designer menu, project creation/selection, folder seeding, and explicit sample record generation actions. Keep automatic conversation analysis for a later stage.

2.9 KiB Raw Permalink Blame History