Active Projects: Tracking & Documentation Infrastructure

[ashleyshaw]

Active Projects Tracking & Documentation

Purpose

Track and document all active projects stored in projects/active/ folder. These are strategic initiatives with deliverables, completion summaries, and implementation notes that need to be:

1. Linked to their corresponding GitHub issues
2. Integrated into team awareness
3. Archived or promoted as work completes

Current Active Projects

1. milestone-planning-v1

• Status: In Progress
• Content: ROADMAP.md (20K), ROADMAP_VISUAL.md (27K)
• Purpose: v1.0 milestone planning infrastructure for versioned releases (v1.0–v1.6)
• Related Issues: feat: implement version-based milestone allocation strategy #1113 (milestone allocation strategy)

2. prd-combined-agent

• Status: Completed ✅
• Version: 2.0.0
• Content: COMPLETION_SUMMARY.md, IMPLEMENTATION_NOTES.md, README.md
• Consolidation: Merged prd-agent + prd-factory-planner-agent (917 files, 144K LOC)
• Related Issues: feat(agents): rewrite PRD Agent for multi-provider support #1094, feat(agents): rewrite PRD Factory Planner Agent for multi-provider support #1095, Epic: Multi-Provider Agent Standardization Initiative #1079 (Epic), feat(agents): Phase 2 Batch 2 - PRD Combined Agent #1196 (PR)

3. repository-maintenance-infrastructure

• Status: Completed ✅
• Version: 1.0.0
• Content: COMPLETION_SUMMARY.md, IMPLEMENTATION_NOTES.md, README.md
• Scope: Automated branch cleanup, permanent maintenance procedures, team documentation
• Related Issues: Epic: Repository Maintenance & Branch Cleanup Automation #1243, Enhance cleanup-branches.js with categorization and --report-only mode #1244, Create permanent maintenance documentation (BRANCH_CLEANUP.md + MAINTENANCE.md) #1245 (tracking issues)
• Related PRs: chore: add .gitignore entries for generated skill directories #1211, docs: comprehensive maintenance & branch cleanup infrastructure #1222, docs: audit changelog consolidation needs — Phase 1 findings & recommendations #1204

Project Goals

• Establish visibility across active work streams
• Link project artifacts to GitHub issue tracking
• Create parent/child issue structure for accountability
• Document project status and dependencies
• Prepare projects for archival or continuation

Definition of Done

• All active projects have GitHub issues
• Project folders linked to parent issues
• Cross-references between projects and PRs documented
• Team aware of active project status
• Archive/continuation decision made for each project

Next Steps

1. Create child issues for each project
2. Link projects to related GitHub issues
3. Update project READMEs with issue references
4. Archive completed projects to projects/archive/ when ready
5. Establish maintenance schedule for active projects

[linear-code]

LS-1793

[github-actions]

⚠️ This issue does not follow a required issue template.

Missing required section(s): Definition of Ready (DoR), Definition of Done (DoD)

The issue will remain open and flagged until the body is corrected.
Please update the issue with one of the official templates:

• https://github.com/lightspeedwp/.github/issues/new/choose

If this was opened by automation, update the automation to preserve the template sections before creating the issue.

[github-actions]

⏱️ Aging and SLA annotation

• Age: 12 day(s)
• SLA state: SLA risk
• Thresholds: warn at 7 days, breach at 14 days
• Last updated: 2026-08-05T11:16:15.316Z

Maintained by project-meta-sync workflow.