Replace broken TODO-to-issue sync with GitHub-native project management by Copilot · Pull Request #64 · devlux76/cortex

Copilot · 2026-03-13T21:10:08Z

The sync-github-project.mjs script and its markdown-driven issue management created 29 issues with overlapping structure (22! combinatorial complexity) and no hierarchy. Agents now have direct gh CLI access, making the intermediary script unnecessary.

Removed

scripts/sync-github-project.mjs (496 lines), its workflow, and npm script

Kept (temporarily)

TODO.md and PLAN.md are retained as reference documentation while GitHub Projects, Milestones, and hierarchical issue structures are established

Added: GitHub-native automation

Issue templates (.github/ISSUE_TEMPLATE/) — structured YAML forms for bugs, features, and implementation tasks with priority/layer dropdowns
PR template — checklist covering lint, typecheck, tests, guard, DESIGN.md
Auto-labeling — actions/labeler with .github/labeler.yml mapping file paths to all 10 CORTEX layer labels
Stale management — actions/stale weekly sweep (60d stale, 14d close, P0/pinned exempt)
Legacy cleanup — one-shot close-legacy-issues.yml workflow (manually triggered) targeting only the 29 specific legacy issue numbers created by the old sync script

Updated docs

copilot-instructions.md — new "Project Management" section directing agents to use gh CLI and GitHub Issues
README.md, DESIGN.md, docs/development.md — updated references to reflect current project management approach

Post-merge

Trigger Actions → "Close Legacy Issues" to close the 29 legacy sync-generated issues, then delete that workflow file.

Original prompt

Here is some advice from CoPilot. We need to implement this advice and take it to the limit to maximize automation and minimize human friction.

Plan it all out in full, then implement it please. Keep in mind we have a broken TODO-to-issue manager that probably just needs to be removed since all agents now have full access to gh command line directly.

The combinatorics on the current issues is basically 22 factoral so structuring them hierarchically is probably not the most direct path on them.

Might be faster and easier to close all open issues as won't fix and drive issue formation and management from a different layer of GitHub itself so the subtask structure is correctly computed and preserved.

From CoPilot:

It sounds like you've built an excellent foundation of organization using markdown files (DESIGN.md, PLAN.md, TODO.md), but you could possibly streamline your workflow by using GitHub's built-in features. Let’s explore some improvements based on your points:

1. Overlapping Issues and Merge Conflicts

Challenge:

Issues like "Task 1" are overarching but lead to merge conflicts when parts of them (e.g., Tasks 2–10) are broken into sub-tasks.
Sub-tasks are competing on the same level in your issue tracking system.

Solution: Organize Projects and Issues Effectively

Use Issue Hierarchies: Convert overarching tasks like "Task 1" into an Epic Issue. Within it, detail the smaller actionable tasks (Tasks 2–10) as checklist items in the description. For long-term organization:
- Use issue linking (mark smaller tasks as Linked Issues) to ensure you can track dependencies and progress.
- Use Milestones to group issues based on phases or sprints.
Breaking Branches Properly: Divide work into feature-specific branches (e.g., feature/task-2) rather than having overlapping branches. During Conflict Fixing, consider rebasing branches regularly to avoid growing divergence.

Relevant GitHub Features:

Issue Checklists: Add tasks in markdown checkboxes in the issue description.
GitHub Projects/Taskboards:
- Set up a project board for your repository.
- Use the Kanban layout to map lifecycle stages (To Do, Doing, Done).
Draft Pull Requests: Open pull requests early for visibility during development.

2. Markdown Files vs GitHub Collaboration Tools

Challenge:

Files like DESIGN.md, PLAN.md, and TODO.md duplicate project management features.
.md files may fall out of sync or clutter the repo, making accountability difficult.

Solution: Replace Markdown Files with Centralized Features

Replace PLAN.md and TODO.md with GitHub Projects:
- Convert to-do items into tasks (issues). Move prioritization to GitHub Projects.
- Track them in an interactive board where you can reorder/assign easily.
Keep DESIGN.md as Proper Documentation:
- Keep this file updated for your source-of-truth architecture, but consider moving more dynamic or front-end-facing details to a README.md or GitHub Wiki.

Relevant GitHub Features:

GitHub Issues as Tasks: Replace ad-hoc .md files with GitHub Issues for collaborative and accountable task-tracking.
Task Assignments and Labels: Use assignees for accountability and labels to classify (e.g., bug, enhancement, priority: high).

3. Scalability and Feature Overlap

Challenge:

Growing complexity is making it hard to manage overlapping tasks, dependencies, and progress while ensuring team coordination.

Solution: Adopt GitHub Automation Where Possible

Automate with GitHub Actions: Set up workflows to automate repetitive tasks (e.g., auto-labeling, CI/CD pipelines, etc.).
Leverage Branch Protection Rules: Use branch protection to enforce proper reviews and avoid improperly merged code.
External Tools: Use tools like ZenHub or Codetree to add additional layers of organization and dependencies, but only once you’ve hit GitHub's limits.

Relevant GitHub Features:

Code Review Process/Protection: Standardize code reviews and require status checks prior to merging.
Dependabot: Use to automate dependency updates.

Summary of Suggestions

High-Level Focus Areas:

Replace .md files for project management (e.g., PLAN.md, TODO.md) with GitHub Issues and Projects.
Organize and link issues hierarchically to eliminate conflict between overarching and dependent tasks.
Automate workflows and enforce process consistency with GitHub Actions and branch protection.

In addition to anything else CoPilot said, just try to derive the most automated system for agentic driven development with accountability that you can. You have all of GitHub's features at your disposal. Configure the repo and its supporting tools with that in mind.

Thanks so much!

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

…ect management - Remove scripts/sync-github-project.mjs and its workflow - Remove TODO.md and PLAN.md (replaced by GitHub Issues/Projects) - Remove sync:github-project npm script - Add issue templates (bug, feature, task) with structured forms - Add PR template with checklist - Add auto-label workflow using actions/labeler with path-based rules - Add close-legacy-issues workflow to close all 29 existing issues - Add stale issue/PR management workflow - Update copilot-instructions.md, README.md, DESIGN.md, docs/development.md Co-authored-by: devlux76 <86517969+devlux76@users.noreply.github.com>

Copilot

Pull request overview

This PR removes the markdown-driven TODO/PLAN → GitHub sync pipeline and replaces it with GitHub-native project management primitives (issue forms, PR template, auto-labeling, and stale automation), updating docs accordingly.

Changes:

Removed TODO.md/PLAN.md and the sync-github-project.mjs script + workflow that attempted to mirror them into GitHub Issues/Milestones/Labels.
Added GitHub-native automation: issue forms, PR template, auto-label workflow + labeler config, stale workflow, and a one-shot legacy issue cleanup workflow.
Updated developer docs and Copilot instructions to direct task tracking into GitHub Issues/Projects instead of repo markdown files.

Reviewed changes

Copilot reviewed 18 out of 18 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
scripts/sync-github-project.mjs	Removed the TODO/PLAN parsing + GitHub API sync script.
.github/workflows/sync-github-project.yml	Removed the workflow that ran the sync script on pushes / dispatch.
package.json	Removed the `sync:github-project` npm script entry.
TODO.md	Removed markdown task tracker (replaced by GitHub Issues/Projects).
PLAN.md	Removed markdown implementation plan tracker (replaced by GitHub Issues/Projects).
docs/development.md	Updated “documentation maintenance” workflow to reference DESIGN/README/api docs + GitHub Issues.
README.md	Added “Project Management” section pointing to Issues/Projects/Milestones/Labels/gh CLI.
DESIGN.md	Removed TODO.md-specific reference while keeping the guard note generic.
.github/workflows/stale.yml	Added weekly stale management for issues/PRs with exemptions.
.github/workflows/auto-label.yml	Added PR auto-labeling via `actions/labeler`.
.github/labeler.yml	Added path→label mappings for the CORTEX layer labels.
.github/copilot-instructions.md	Updated instructions to use GitHub-native project management instead of markdown tracking.
.github/PULL_REQUEST_TEMPLATE.md	Added PR checklist (lint/typecheck/tests/guard/docs).
.github/workflows/close-legacy-issues.yml	Added a manually-triggered workflow intended to close legacy sync-created issues.
.github/ISSUE_TEMPLATE/*	Added YAML issue forms for task/feature/bug plus template config.

devlux76 · 2026-03-13T21:44:51Z

+            // Paginate through all open issues
+            let page = 1;
+            let closed = 0;
+            while (true) {
+              const { data: issues } = await github.rest.issues.listForRepo({
+                owner, repo,
+                state: "open",
+                per_page: 100,
+                page,
+              });
+              if (issues.length === 0) break;
+
+              for (const issue of issues) {
+                // Skip pull requests (they appear in the issues API)
+                if (issue.pull_request) continue;
+
+                await github.rest.issues.addLabels({
+                  owner, repo,
+                  issue_number: issue.number,
+                  labels: ["wontfix"],
+                });
+                await github.rest.issues.update({
+                  owner, repo,
+                  issue_number: issue.number,
+                  state: "closed",
+                  state_reason: "not_planned",
+                });


@copilot we may need to do this in steps. Removing the PLAN and TODO at this stage is not as important as simply closing the issues right now.

If possible the best path is to close the issues while keeping the files temporarily while we figure out what to do with them.

We need issues, just not these issues in this form.

At core we need all PRs to speak to actual issues, tasks and subtasks.

To do that, we need those need to be organized hierarchically from the top down.

Can we look to Projects, Milestones and other canonical GitHub project management structures, get those in place before we delete the docs which were quite frankly a lot of effort and expense to get this far?

Restored TODO.md and PLAN.md in 49ea771. The close-legacy-issues workflow now targets only the 29 specific issue numbers ([21, 23–42, 56–63]) created by the old sync script, so it won't affect any new issues created afterward. The broken sync-github-project.mjs script and its workflow are still removed, and all the new GitHub-native automation (issue templates, PR template, auto-labeling, stale management) is in place ready to go alongside the existing docs.

…list - Restore TODO.md and PLAN.md (keep existing docs while GitHub-native project management is set up) - Rewrite close-legacy-issues.yml to only close the 29 specific issues created by the old sync script, not all future issues - Restore PLAN.md/TODO.md rows in README.md and copilot-instructions.md Co-authored-by: devlux76 <86517969+devlux76@users.noreply.github.com>

Initial plan

2c6b8c8

Copilot AI assigned Copilot and devlux76 Mar 13, 2026

Copilot started work on behalf of devlux76 March 13, 2026 21:10 View session

Copilot AI changed the title ~~[WIP] Remove broken TODO-to-issue manager for improved automation~~ Replace broken TODO-to-issue sync with GitHub-native project management Mar 13, 2026

Copilot AI requested a review from devlux76 March 13, 2026 21:19

Copilot finished work on behalf of devlux76 March 13, 2026 21:19

github-actions Bot added layer: ci CI/CD pipeline and build tooling layer: documentation API docs, developer guide, architecture diagrams labels Mar 13, 2026

devlux76 marked this pull request as ready for review March 13, 2026 21:28

Copilot AI review requested due to automatic review settings March 13, 2026 21:28

Copilot started reviewing on behalf of devlux76 March 13, 2026 21:28 View session

Copilot AI reviewed Mar 13, 2026

View reviewed changes

Copilot started work on behalf of devlux76 March 13, 2026 21:44 View session

Copilot finished work on behalf of devlux76 March 13, 2026 21:49

devlux76 merged commit 762b556 into main Mar 13, 2026
3 checks passed

devlux76 deleted the copilot/remove-broken-todo-issue-manager branch March 13, 2026 21:54

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Replace broken TODO-to-issue sync with GitHub-native project management#64

Replace broken TODO-to-issue sync with GitHub-native project management#64
devlux76 merged 3 commits intomainfrom
copilot/remove-broken-todo-issue-manager

Copilot AI commented Mar 13, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

devlux76 Mar 13, 2026

Uh oh!

Copilot AI Mar 13, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

Copilot AI commented Mar 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Removed

Kept (temporarily)

Added: GitHub-native automation

Updated docs

Post-merge

1. Overlapping Issues and Merge Conflicts

Challenge:

Solution: Organize Projects and Issues Effectively

Relevant GitHub Features:

2. Markdown Files vs GitHub Collaboration Tools

Challenge:

Solution: Replace Markdown Files with Centralized Features

Relevant GitHub Features:

3. Scalability and Feature Overlap

Challenge:

Solution: Adopt GitHub Automation Where Possible

Relevant GitHub Features:

Summary of Suggestions

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

devlux76 Mar 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 13, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Mar 13, 2026 •

edited

Loading