Project planner: daily roadmap discussion from issues and PRs

Runs the same job in your agent session, on the plan you are signed in with. No API key, no Action.

Do the job of the "Project planner: daily roadmap discussion from issues and PRs" workflow from AgentFlows (https://agentflows.sh/flows/agentics-plan) right here, in this session, using the plan I'm signed in with. No API key and no GitHub Action.

Install these agent skills first. Download each SKILL.md from its source (respect its license) into .claude/skills/<name>/SKILL.md, or wherever this agent loads skills from:
- Planning and task breakdown: spec to ordered tasks: https://github.com/addyosmani/agent-skills/tree/main/skills/planning-and-task-breakdown (MIT), notes at https://agentflows.sh/skills/addyosmani-planning-and-task-breakdown

What it does: Runs daily. The agent reviews open issues, pull requests and recent work, then creates or updates a planning discussion with a prioritized roadmap and suggested new issues. It reads maintainer comments on the plan.

The workflow normally runs on: schedule: daily + workflow_dispatch. Instead, ask me which pull request, issue, or branch to work on, then follow these instructions:

```text
# Agentic Planner

## Job Description

Your job is to act as a planner for the GitHub repository ${{ github.repository }}.

1. First study the state of the repository including, open issues, pull requests, completed issues.

   1a. As part of this, look for the open discussion with title starting with "[plan]", which is the existing project plan. Read the plan, and any comments on the plan. If no such discussion exists, ignore this step.

   1b. You can read code, search the web and use other tools to help you understand the project and its requirements.

2. Formulate a plan for the remaining work to achieve the objectives of the project.

   2a. The project plan should be a clear, concise, succinct summary of the current state of the project, including the issues that need to be completed, their priority, and any dependencies between them.

   2b. The project plan should be written into the discussion body itself, not as a comment. If comments have been added to the project plan, take them into account and note this in the project plan. Never add comments to the project plan discussion.

   2c. In the plan, list suggested issues to create to match the proposed updated plan. Don't create any issues, just list the suggestions. Do this by showing `gh` commands to create the issues with labels and complete bodies, but don't actually create them. Don't include suggestions for issues that already exist, only new things required as part of the plan!

3. Create a new planning discussion with the project plan in its body. 

   3a. Create a discussion with an appropriate title starting with "[plan]" and the current date (e.g., "[plan] 2025-10-10"), using the project plan as the body.
```

Use the gh CLI for anything on GitHub, and show me what you plan to post or change before you do it.