Brainstorming: Integrate remaining general concepts into specification

[frankbria]

Overview

Review and integrate the 6 remaining general concepts from CONCEPTS_INTEGRATION.md into CODEFRAME_SPEC.md and AGILE_SPRINTS.md after brainstorming session.

Background

Created comprehensive analysis in CONCEPTS_INTEGRATION.md comparing 10 general concept ideas against existing specification. Found:

• ✅ 6 concepts already implemented
• 📝 6 concepts need specification enhancement
• ❓ 3 clarification questions need answers

Concepts Requiring Integration

1. Claude Code Hook Integration (P1, Sprint 6/8)

• Concept: Use before_compact hook to write status and next steps
• Gap: Specific hook integration not in spec (Flash Save system exists)
• Action: Add Section 7.3 with hook implementation details

2. Replan Command (P1, Sprint 2)

• Concept: Command to "re-engineer" the issue/task list
• Gap: CLI command not specified
• Action: Add codeframe replan command to CLI specification

3. Task Checklists (P1, Sprint 2)

• Concept: Connection between issue list and todo list
• Gap: Tasks have dependencies but not sub-task checklists
• Action: Enhance tasks table with checklist_items JSON field

4. Agent Skills Registry (P2, Sprint 4/Post-MVP)

• Concept: Leverage skills from agent libraries (e.g., Superpowers)
• Gap: No extensible agent capability system
• Action: Add agent skills registry section and database schema

5. Codebase Indexing (P1, Sprint 3/6)

• Concept: Where is index of codebase stored?
• Gap: Virtual Project has context but no structural index
• Action: Add Section 3.4 with codebase_index table and AST parsing

6. Git Branching Strategy (P1, Sprint 3/8)

• Concept: Special branches for deployment, migration
• Gap: No git workflow specified
• Action: Add Section 9.5 with branching model (feature/staging/production)

Clarification Questions

Before integration, need answers to:

1. Issues vs Tasks: Are "issues" different from "tasks", or same concept?

   • Current spec uses "tasks" table for work items
   • Should we add separate "issues" table or are they synonymous?

2. Subagent Terminology: Does "subagent" mean "Worker Agent"?

   • Spec uses "Worker Agents" (Backend, Frontend, Test, Review)
   • Confirm terminology alignment

3. Agent Library Priority: How important is extensible agent system for MVP?

   • Affects whether this goes in Sprint 4 or post-MVP
   • Determines P1 vs P2 priority

Proposed Process

1. Brainstorming Session (at least once):

   • Review CONCEPTS_INTEGRATION.md together
   • Answer 3 clarification questions
   • Decide which concepts to integrate
   • Confirm priorities and sprint assignments

2. Specification Updates:

   • Update CODEFRAME_SPEC.md with approved sections
   • Add proposed database schemas
   • Enhance CLI command documentation
   • Add code examples where helpful

3. Sprint Plan Updates:

   • Add new tasks to AGILE_SPRINTS.md
   • Assign effort estimates
   • Update sprint capacity planning

Files Involved

• CONCEPTS_INTEGRATION.md - Complete analysis (reference)
• CODEFRAME_SPEC.md - Technical specification (to update)
• AGILE_SPRINTS.md - Implementation plan (to update)

Success Criteria

• All 3 clarification questions answered
• Decision made on each of 6 concepts (integrate or defer)
• CODEFRAME_SPEC.md updated with approved concepts
• AGILE_SPRINTS.md updated with new tasks
• Priorities and sprint assignments confirmed
• No duplicate features (already-implemented concepts remain unchanged)

Next Steps

1. Schedule brainstorming review session
2. Review CONCEPTS_INTEGRATION.md analysis
3. Answer clarification questions
4. Make integration decisions
5. Update specifications

[traycerai]

Plan

Observations

The task is to integrate 6 remaining general concepts from CONCEPTS_INTEGRATION.md into the CodeFRAME specification and sprint plan documents. The analysis has identified which concepts are already implemented (no action needed) and which require specification enhancements. Three clarification questions have been answered, and priorities have been assigned (P1/P2/P3). The goal is to update documentation to reflect the enhanced feature set while maintaining consistency and avoiding duplication.

Approach

Update CODEFRAME_SPEC.md with new sections for approved concepts (codebase indexing, git branching, Claude Code hooks, replan command, task checklists), enhance database schema, and add CLI commands. Then update AGILE_SPRINTS.md with new tasks distributed across appropriate sprints with effort estimates. Finally, update CONCEPTS_INTEGRATION.md to mark the integration as complete and document decisions made.

Reasoning

Listed the repository structure to understand the project layout, then read the three key files (CONCEPTS_INTEGRATION.md, CODEFRAME_SPEC.md, and AGILE_SPRINTS.md) to understand the current state, the analysis of concepts, and the implementation plan. Analyzed the gaps and provided recommendations for which concepts to integrate based on priority and MVP requirements.

Proposed File Changes

📄 CODEFRAME_SPEC.md ^(MODIFY) 🔗

References

• 📄 CONCEPTS_INTEGRATION.md ^(MODIFY)

Add new Section 3.4 "Codebase Indexing" after the existing Section 3.3 (around line 162). This section should include:

• Purpose statement explaining why agents need structural awareness of the codebase
• Database schema for codebase_index table with fields: id, project_id, file_path, file_type, language, symbols (JSON), imports (JSON), loc, last_modified, content_hash
• JSON structure examples for symbols (classes, functions, exports) and imports
• Indexing process description covering AST parsing for Python/TypeScript/JavaScript
• Agent usage API examples: index.find_symbol(), index.find_importers(), index.get_tree_view()
• Update strategy: incremental re-indexing based on content hash comparison
• Triggers: after git commits, file writes, scheduled background re-index

Add new Section 7.3 "Claude Code Hook Integration" after Section 7.2 (around line 623). This section should include:

• Hook type specification: before_compact (pre-compactification trigger)
• Implementation details for .claude/hooks/before_compact.sh script
• Integration with existing Flash Save system from Section 7
• Output format for session handoff file (.codeframe/session_handoff.md) with current state, pending blockers, next steps, and context preservation details
• CLI command integration: codeframe checkpoint create --trigger "pre_compact" --auto

Add new Section 9.5 "Git Workflow & Branching Strategy" after Section 9.4 or at end of Section 9 (around line 771). This section should include:

• Default branch strategy diagram showing main, dev, staging, production branches
• Feature branch naming convention: feature/task-{id}-{slug}
• Branch management workflow for starting and completing tasks
• Special branch types: migration branches (migration/vX.Y) and deployment branches (deploy/{env})
• Migration handling process with automated script generation and testing
• Deployment process with environment-specific branches, tagging, and rollback support
• Configuration JSON structure for git workflow settings
• CLI commands: codeframe deploy, codeframe deploy rollback, codeframe migrate

Enhance Section 13 "API Specifications" (around line 986) by adding the codeframe replan command to the CLI commands list:

• Command syntax: codeframe replan [--from-prd] [--keep-completed] [--interactive]
• Options documentation explaining each flag
• Use cases: PRD changed, blocked path, scope adjustment, dependency issues
• Lead Agent behavior during replanning: analyze progress, re-read PRD, preserve completed tasks, generate new decomposition, merge with existing tasks, update dependencies, notify agents

Enhance Database Schema section (around line 854) by:

• Adding the codebase_index table schema as specified in Section 3.4
• Modifying the tasks table to add checklist_items JSON field for subtask tracking
• Adding example JSON structure for checklist items: {"items": [{"id": 1, "description": "...", "completed": true}], "completion": "1/3"}
• Optionally adding task_type field to tasks table with CHECK constraint for values: 'feature', 'bug', 'enhancement', 'tech_debt', 'question'

Update Glossary in Appendix (around line 1320) to add:

• Entry clarifying that "Issues" and "Tasks" are the same concept in CodeFRAME
• Entry defining "Subagent" as synonymous with "Worker Agent"
• Entry for "Codebase Index" explaining the structural awareness system
• Entry for "Replan" explaining the adaptive planning capability

📄 AGILE_SPRINTS.md ^(MODIFY) 🔗

References

• 📄 CONCEPTS_INTEGRATION.md ^(MODIFY)
• 📄 CODEFRAME_SPEC.md ^(MODIFY)

Enhance Sprint 2: Socratic Discovery (around line 557) by adding new tasks:

• Task cf-14.5: "Replan Command Implementation" (3-4 hours)

  • Add CLI command codeframe replan with options --from-prd, --keep-completed, --interactive
  • Implement Lead Agent replanning logic to re-analyze PRD and regenerate task list
  • Preserve completed tasks and merge with new decomposition
  • Update task dependencies based on new plan
  • Send WebSocket notifications to agents about task changes
  • Dependencies: Requires cf-14 (Task Decomposition) to be complete
  • Acceptance criteria: User can trigger replanning, completed work is preserved, new tasks are generated, agents are notified

• Task cf-14.6: "Task Checklist Support" (2-3 hours)

  • Add checklist_items JSON field to tasks table schema
  • Update task creation/update API to handle checklist items
  • Implement checklist completion tracking logic
  • Add UI display for task checklists in dashboard
  • Dependencies: None (can run in parallel with other Sprint 2 tasks)
  • Acceptance criteria: Tasks can have sub-checklists, completion percentage is tracked, UI displays checklist progress

Update Sprint 2 effort estimate from current total to add 5-7 hours for new tasks.

Enhance Sprint 3: Single Agent Execution (around line 626) by adding new tasks:

• Task cf-18.5: "Codebase Indexing System" (4-6 hours)

  • Create codebase_index table in database schema
  • Implement AST parsing for Python, TypeScript, and JavaScript files
  • Build symbol extraction logic (classes, functions, exports)
  • Build import dependency graph extraction
  • Implement incremental re-indexing based on content hash
  • Create agent query API: find_symbol(), find_importers(), get_tree_view()
  • Add background re-indexing scheduler (every 5 minutes during active work)
  • Dependencies: Requires database setup from Sprint 1
  • Acceptance criteria: Agents can query codebase structure without reading full files, index updates automatically on file changes

• Task cf-44.5: "Git Branching Strategy" (4-6 hours)

  • Implement feature branch creation per task: feature/task-{id}-{slug}
  • Add branch management to task start/complete workflow
  • Implement environment branch support (dev, staging, production)
  • Add migration branch handling with automated script generation
  • Implement deployment branch workflow with tagging and rollback
  • Add CLI commands: codeframe deploy, codeframe deploy rollback, codeframe migrate
  • Update git integration configuration schema
  • Dependencies: Requires basic git integration from Sprint 3
  • Acceptance criteria: Tasks automatically create feature branches, deployment to staging/production works, migrations have dedicated branches

Update Sprint 3 effort estimate to add 8-12 hours for new tasks. Note that cf-44.5 could alternatively be moved to Sprint 8 if git branching is not needed for MVP.

Enhance Sprint 6: Context Management (around line 837) by adding new task:

• Task cf-36.5: "Claude Code Hook Integration" (2-3 hours)
  • Create .claude/hooks/before_compact.sh hook script
  • Integrate hook with existing Flash Save system from Sprint 6
  • Implement session handoff file generation (.codeframe/session_handoff.md)
  • Add hook execution logging
  • Test hook triggers before compactification
  • Dependencies: Requires Flash Save system (cf-36) to be complete
  • Acceptance criteria: Hook triggers automatically before compactification, session handoff file is created, flash save checkpoint is created, agents can resume seamlessly

Update Sprint 6 effort estimate to add 2-3 hours for new task.

Add note to Post-MVP Sprints section (around line 1174) documenting deferred concepts:

• Sprint 9+: Agent Skills Registry (Post-MVP)

  • Extensible agent capability system
  • Custom agent plugin architecture
  • Agent marketplace/registry
  • Skill-based task matching beyond hardcoded agent types
  • Priority: P3 (defer until users request custom agent types)

• Sprint 9+: GitHub Integration (Post-MVP)

  • Bidirectional sync between CodeFRAME tasks and GitHub Issues
  • GitHub PR linking to tasks
  • GitHub comment import to memory table
  • CLI commands: codeframe github sync, codeframe github push, codeframe github pull
  • Priority: P3 (nice to have, not critical for MVP)

Update MVP Success Criteria section (around line 1139) to include new capabilities:

• Codebase indexing enables efficient agent navigation
• Replan command allows adaptive planning when requirements change
• Git branching strategy supports production deployments
• Task checklists enable breakdown of complex work items
• Claude Code hooks preserve context across compactification

📄 CONCEPTS_INTEGRATION.md ^(MODIFY) 🔗

References

• 📄 CODEFRAME_SPEC.md ^(MODIFY)
• 📄 AGILE_SPRINTS.md ^(MODIFY)

Update the Document Status section at the bottom (around line 837) to reflect completion:

• Change status from "Draft for User Review" to "Integration Complete"
• Update "Last Updated" date to current date
• Change "Next Action" from "Await user feedback and clarifications" to "Specifications updated, ready for implementation"

Add new Integration Decisions section after the Summary (around line 786) documenting the decisions made:

• Clarification Question 1 (Issues vs Tasks): Decision made to keep as same concept using existing tasks table. Added optional task_type field to distinguish feature/bug/enhancement/tech_debt if needed.

• Clarification Question 2 (Subagent terminology): Confirmed "subagent" means "Worker Agent". Standardized on "Worker Agent" terminology throughout documentation. Added glossary entry noting synonyms.

• Clarification Question 3 (Agent Library priority): Decision made to implement basic skill matching in Sprint 4 (P1) and defer extensible registry to Post-MVP (P3). MVP will hardcode 4 agent types (Backend, Frontend, Test, Review).

• Integration Priority Decisions:

  • P1 (Integrated into MVP): Codebase Indexing (Sprint 3), Replan Command (Sprint 2), Git Branching Strategy (Sprint 3)
  • P2 (Integrated into MVP): Task Checklists (Sprint 2), Claude Code Hooks (Sprint 6)
  • P3 (Deferred to Post-MVP): Agent Skills Registry (Sprint 9+)

Update the Summary of Integration Actions section (around line 786) to mark completed items:

• Change section title to "Summary of Integration Actions (COMPLETED)"
• Add checkmarks to all "Specification Enhancements Needed" items showing they've been integrated
• Add note: "All P1 and P2 concepts have been integrated into CODEFRAME_SPEC.md and AGILE_SPRINTS.md. P3 concepts documented for Post-MVP consideration."

Add new Files Updated section listing the changes made:

• CODEFRAME_SPEC.md: Added Sections 3.4, 7.3, 9.5, enhanced Section 13 and database schema, updated glossary
• AGILE_SPRINTS.md: Added tasks cf-14.5, cf-14.6 (Sprint 2), cf-18.5, cf-44.5 (Sprint 3), cf-36.5 (Sprint 6), documented Post-MVP deferrals
• CONCEPTS_INTEGRATION.md: Updated status to reflect integration completion and decisions made

Diagram

sequenceDiagram
    participant User
    participant CONCEPTS_INTEGRATION.md
    participant CODEFRAME_SPEC.md
    participant AGILE_SPRINTS.md
    
    User->>CONCEPTS_INTEGRATION.md: Review analysis & recommendations
    User->>User: Answer 3 clarification questions
    User->>User: Approve P1/P2/P3 priorities
    
    Note over CODEFRAME_SPEC.md: Add New Sections
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Section 3.4: Codebase Indexing
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Section 7.3: Claude Code Hooks
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Section 9.5: Git Branching Strategy
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Enhance Section 13: Add replan command
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Enhance DB Schema: Add codebase_index table
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Enhance DB Schema: Add checklist_items to tasks
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Update Glossary: Issues=Tasks, Subagent=Worker
    
    Note over AGILE_SPRINTS.md: Add New Tasks
    CONCEPTS_INTEGRATION.md->>AGILE_SPRINTS.md: Sprint 2: cf-14.5 (Replan), cf-14.6 (Checklists)
    CONCEPTS_INTEGRATION.md->>AGILE_SPRINTS.md: Sprint 3: cf-18.5 (Indexing), cf-44.5 (Git)
    CONCEPTS_INTEGRATION.md->>AGILE_SPRINTS.md: Sprint 6: cf-36.5 (Hooks)
    CONCEPTS_INTEGRATION.md->>AGILE_SPRINTS.md: Post-MVP: Agent Registry, GitHub Sync
    CONCEPTS_INTEGRATION.md->>AGILE_SPRINTS.md: Update effort estimates per sprint
    
    Note over CONCEPTS_INTEGRATION.md: Mark Complete
    CODEFRAME_SPEC.md->>CONCEPTS_INTEGRATION.md: Document decisions made
    AGILE_SPRINTS.md->>CONCEPTS_INTEGRATION.md: Document integration status
    CONCEPTS_INTEGRATION.md->>CONCEPTS_INTEGRATION.md: Update status to "Integration Complete"
    
    CONCEPTS_INTEGRATION.md->>User: Integration complete, ready for implementation

Loading

Import In IDE

🤖 Prompt for AI Agents

I have created the following plan after thorough exploration and analysis of the codebase. Follow the below plan verbatim. Trust the files and references. Do not re-verify what's written in the plan. Explore only when absolutely necessary. First implement all the proposed file changes and then I'll review all the changes together at the end.

### Observations

The task is to integrate 6 remaining general concepts from `CONCEPTS_INTEGRATION.md` into the CodeFRAME specification and sprint plan documents. The analysis has identified which concepts are already implemented (no action needed) and which require specification enhancements. Three clarification questions have been answered, and priorities have been assigned (P1/P2/P3). The goal is to update documentation to reflect the enhanced feature set while maintaining consistency and avoiding duplication.

### Approach

Update `CODEFRAME_SPEC.md` with new sections for approved concepts (codebase indexing, git branching, Claude Code hooks, replan command, task checklists), enhance database schema, and add CLI commands. Then update `AGILE_SPRINTS.md` with new tasks distributed across appropriate sprints with effort estimates. Finally, update `CONCEPTS_INTEGRATION.md` to mark the integration as complete and document decisions made.

### Reasoning

Listed the repository structure to understand the project layout, then read the three key files (`CONCEPTS_INTEGRATION.md`, `CODEFRAME_SPEC.md`, and `AGILE_SPRINTS.md`) to understand the current state, the analysis of concepts, and the implementation plan. Analyzed the gaps and provided recommendations for which concepts to integrate based on priority and MVP requirements.

## Mermaid Diagram

sequenceDiagram
    participant User
    participant CONCEPTS_INTEGRATION.md
    participant CODEFRAME_SPEC.md
    participant AGILE_SPRINTS.md
    
    User->>CONCEPTS_INTEGRATION.md: Review analysis & recommendations
    User->>User: Answer 3 clarification questions
    User->>User: Approve P1/P2/P3 priorities
    
    Note over CODEFRAME_SPEC.md: Add New Sections
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Section 3.4: Codebase Indexing
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Section 7.3: Claude Code Hooks
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Section 9.5: Git Branching Strategy
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Enhance Section 13: Add replan command
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Enhance DB Schema: Add codebase_index table
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Enhance DB Schema: Add checklist_items to tasks
    CONCEPTS_INTEGRATION.md->>CODEFRAME_SPEC.md: Update Glossary: Issues=Tasks, Subagent=Worker
    
    Note over AGILE_SPRINTS.md: Add New Tasks
    CONCEPTS_INTEGRATION.md->>AGILE_SPRINTS.md: Sprint 2: cf-14.5 (Replan), cf-14.6 (Checklists)
    CONCEPTS_INTEGRATION.md->>AGILE_SPRINTS.md: Sprint 3: cf-18.5 (Indexing), cf-44.5 (Git)
    CONCEPTS_INTEGRATION.md->>AGILE_SPRINTS.md: Sprint 6: cf-36.5 (Hooks)
    CONCEPTS_INTEGRATION.md->>AGILE_SPRINTS.md: Post-MVP: Agent Registry, GitHub Sync
    CONCEPTS_INTEGRATION.md->>AGILE_SPRINTS.md: Update effort estimates per sprint
    
    Note over CONCEPTS_INTEGRATION.md: Mark Complete
    CODEFRAME_SPEC.md->>CONCEPTS_INTEGRATION.md: Document decisions made
    AGILE_SPRINTS.md->>CONCEPTS_INTEGRATION.md: Document integration status
    CONCEPTS_INTEGRATION.md->>CONCEPTS_INTEGRATION.md: Update status to "Integration Complete"
    
    CONCEPTS_INTEGRATION.md->>User: Integration complete, ready for implementation

## Proposed File Changes

### CODEFRAME_SPEC.md(MODIFY)

References: 

- CONCEPTS_INTEGRATION.md(MODIFY)

Add new **Section 3.4 "Codebase Indexing"** after the existing Section 3.3 (around line 162). This section should include:

- Purpose statement explaining why agents need structural awareness of the codebase
- Database schema for `codebase_index` table with fields: id, project_id, file_path, file_type, language, symbols (JSON), imports (JSON), loc, last_modified, content_hash
- JSON structure examples for symbols (classes, functions, exports) and imports
- Indexing process description covering AST parsing for Python/TypeScript/JavaScript
- Agent usage API examples: `index.find_symbol()`, `index.find_importers()`, `index.get_tree_view()`
- Update strategy: incremental re-indexing based on content hash comparison
- Triggers: after git commits, file writes, scheduled background re-index

Add new **Section 7.3 "Claude Code Hook Integration"** after Section 7.2 (around line 623). This section should include:

- Hook type specification: `before_compact` (pre-compactification trigger)
- Implementation details for `.claude/hooks/before_compact.sh` script
- Integration with existing Flash Save system from Section 7
- Output format for session handoff file (`.codeframe/session_handoff.md`) with current state, pending blockers, next steps, and context preservation details
- CLI command integration: `codeframe checkpoint create --trigger "pre_compact" --auto`

Add new **Section 9.5 "Git Workflow & Branching Strategy"** after Section 9.4 or at end of Section 9 (around line 771). This section should include:

- Default branch strategy diagram showing main, dev, staging, production branches
- Feature branch naming convention: `feature/task-{id}-{slug}`
- Branch management workflow for starting and completing tasks
- Special branch types: migration branches (`migration/vX.Y`) and deployment branches (`deploy/{env}`)
- Migration handling process with automated script generation and testing
- Deployment process with environment-specific branches, tagging, and rollback support
- Configuration JSON structure for git workflow settings
- CLI commands: `codeframe deploy`, `codeframe deploy rollback`, `codeframe migrate`

Enhance **Section 13 "API Specifications"** (around line 986) by adding the `codeframe replan` command to the CLI commands list:

- Command syntax: `codeframe replan [--from-prd] [--keep-completed] [--interactive]`
- Options documentation explaining each flag
- Use cases: PRD changed, blocked path, scope adjustment, dependency issues
- Lead Agent behavior during replanning: analyze progress, re-read PRD, preserve completed tasks, generate new decomposition, merge with existing tasks, update dependencies, notify agents

Enhance **Database Schema section** (around line 854) by:

- Adding the `codebase_index` table schema as specified in Section 3.4
- Modifying the `tasks` table to add `checklist_items` JSON field for subtask tracking
- Adding example JSON structure for checklist items: `{"items": [{"id": 1, "description": "...", "completed": true}], "completion": "1/3"}`
- Optionally adding `task_type` field to tasks table with CHECK constraint for values: 'feature', 'bug', 'enhancement', 'tech_debt', 'question'

Update **Glossary in Appendix** (around line 1320) to add:

- Entry clarifying that "Issues" and "Tasks" are the same concept in CodeFRAME
- Entry defining "Subagent" as synonymous with "Worker Agent"
- Entry for "Codebase Index" explaining the structural awareness system
- Entry for "Replan" explaining the adaptive planning capability

### AGILE_SPRINTS.md(MODIFY)

References: 

- CONCEPTS_INTEGRATION.md(MODIFY)
- CODEFRAME_SPEC.md(MODIFY)

Enhance **Sprint 2: Socratic Discovery** (around line 557) by adding new tasks:

- **Task cf-14.5**: "Replan Command Implementation" (3-4 hours)
  - Add CLI command `codeframe replan` with options --from-prd, --keep-completed, --interactive
  - Implement Lead Agent replanning logic to re-analyze PRD and regenerate task list
  - Preserve completed tasks and merge with new decomposition
  - Update task dependencies based on new plan
  - Send WebSocket notifications to agents about task changes
  - Dependencies: Requires cf-14 (Task Decomposition) to be complete
  - Acceptance criteria: User can trigger replanning, completed work is preserved, new tasks are generated, agents are notified

- **Task cf-14.6**: "Task Checklist Support" (2-3 hours)
  - Add `checklist_items` JSON field to tasks table schema
  - Update task creation/update API to handle checklist items
  - Implement checklist completion tracking logic
  - Add UI display for task checklists in dashboard
  - Dependencies: None (can run in parallel with other Sprint 2 tasks)
  - Acceptance criteria: Tasks can have sub-checklists, completion percentage is tracked, UI displays checklist progress

Update Sprint 2 effort estimate from current total to add 5-7 hours for new tasks.

Enhance **Sprint 3: Single Agent Execution** (around line 626) by adding new tasks:

- **Task cf-18.5**: "Codebase Indexing System" (4-6 hours)
  - Create `codebase_index` table in database schema
  - Implement AST parsing for Python, TypeScript, and JavaScript files
  - Build symbol extraction logic (classes, functions, exports)
  - Build import dependency graph extraction
  - Implement incremental re-indexing based on content hash
  - Create agent query API: find_symbol(), find_importers(), get_tree_view()
  - Add background re-indexing scheduler (every 5 minutes during active work)
  - Dependencies: Requires database setup from Sprint 1
  - Acceptance criteria: Agents can query codebase structure without reading full files, index updates automatically on file changes

- **Task cf-44.5**: "Git Branching Strategy" (4-6 hours)
  - Implement feature branch creation per task: `feature/task-{id}-{slug}`
  - Add branch management to task start/complete workflow
  - Implement environment branch support (dev, staging, production)
  - Add migration branch handling with automated script generation
  - Implement deployment branch workflow with tagging and rollback
  - Add CLI commands: `codeframe deploy`, `codeframe deploy rollback`, `codeframe migrate`
  - Update git integration configuration schema
  - Dependencies: Requires basic git integration from Sprint 3
  - Acceptance criteria: Tasks automatically create feature branches, deployment to staging/production works, migrations have dedicated branches

Update Sprint 3 effort estimate to add 8-12 hours for new tasks. Note that cf-44.5 could alternatively be moved to Sprint 8 if git branching is not needed for MVP.

Enhance **Sprint 6: Context Management** (around line 837) by adding new task:

- **Task cf-36.5**: "Claude Code Hook Integration" (2-3 hours)
  - Create `.claude/hooks/before_compact.sh` hook script
  - Integrate hook with existing Flash Save system from Sprint 6
  - Implement session handoff file generation (`.codeframe/session_handoff.md`)
  - Add hook execution logging
  - Test hook triggers before compactification
  - Dependencies: Requires Flash Save system (cf-36) to be complete
  - Acceptance criteria: Hook triggers automatically before compactification, session handoff file is created, flash save checkpoint is created, agents can resume seamlessly

Update Sprint 6 effort estimate to add 2-3 hours for new task.

Add note to **Post-MVP Sprints section** (around line 1174) documenting deferred concepts:

- **Sprint 9+: Agent Skills Registry** (Post-MVP)
  - Extensible agent capability system
  - Custom agent plugin architecture
  - Agent marketplace/registry
  - Skill-based task matching beyond hardcoded agent types
  - Priority: P3 (defer until users request custom agent types)

- **Sprint 9+: GitHub Integration** (Post-MVP)
  - Bidirectional sync between CodeFRAME tasks and GitHub Issues
  - GitHub PR linking to tasks
  - GitHub comment import to memory table
  - CLI commands: `codeframe github sync`, `codeframe github push`, `codeframe github pull`
  - Priority: P3 (nice to have, not critical for MVP)

Update **MVP Success Criteria** section (around line 1139) to include new capabilities:

- Codebase indexing enables efficient agent navigation
- Replan command allows adaptive planning when requirements change
- Git branching strategy supports production deployments
- Task checklists enable breakdown of complex work items
- Claude Code hooks preserve context across compactification

### CONCEPTS_INTEGRATION.md(MODIFY)

References: 

- CODEFRAME_SPEC.md(MODIFY)
- AGILE_SPRINTS.md(MODIFY)

Update the **Document Status** section at the bottom (around line 837) to reflect completion:

- Change status from "Draft for User Review" to "Integration Complete"
- Update "Last Updated" date to current date
- Change "Next Action" from "Await user feedback and clarifications" to "Specifications updated, ready for implementation"

Add new **Integration Decisions** section after the Summary (around line 786) documenting the decisions made:

- **Clarification Question 1 (Issues vs Tasks)**: Decision made to keep as same concept using existing tasks table. Added optional `task_type` field to distinguish feature/bug/enhancement/tech_debt if needed.

- **Clarification Question 2 (Subagent terminology)**: Confirmed "subagent" means "Worker Agent". Standardized on "Worker Agent" terminology throughout documentation. Added glossary entry noting synonyms.

- **Clarification Question 3 (Agent Library priority)**: Decision made to implement basic skill matching in Sprint 4 (P1) and defer extensible registry to Post-MVP (P3). MVP will hardcode 4 agent types (Backend, Frontend, Test, Review).

- **Integration Priority Decisions**:
  - P1 (Integrated into MVP): Codebase Indexing (Sprint 3), Replan Command (Sprint 2), Git Branching Strategy (Sprint 3)
  - P2 (Integrated into MVP): Task Checklists (Sprint 2), Claude Code Hooks (Sprint 6)
  - P3 (Deferred to Post-MVP): Agent Skills Registry (Sprint 9+)

Update the **Summary of Integration Actions** section (around line 786) to mark completed items:

- Change section title to "Summary of Integration Actions (COMPLETED)"
- Add checkmarks to all "Specification Enhancements Needed" items showing they've been integrated
- Add note: "All P1 and P2 concepts have been integrated into CODEFRAME_SPEC.md and AGILE_SPRINTS.md. P3 concepts documented for Post-MVP consideration."

Add new **Files Updated** section listing the changes made:

- `CODEFRAME_SPEC.md`: Added Sections 3.4, 7.3, 9.5, enhanced Section 13 and database schema, updated glossary
- `AGILE_SPRINTS.md`: Added tasks cf-14.5, cf-14.6 (Sprint 2), cf-18.5, cf-44.5 (Sprint 3), cf-36.5 (Sprint 6), documented Post-MVP deferrals
- `CONCEPTS_INTEGRATION.md`: Updated status to reflect integration completion and decisions made

---

Developer Humor

🎯 Six concepts walked into a spec,
Three said P1! and got respect,
Two said P2, we're nice to have!
One said Post-MVP and took a nap.
The database grew, the sprints aligned,
And CodeFRAME's future was redefined! 📚✨

---

Execution Information

Branch: main
Commit: 77079a9

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.