schedule-backlog

Étoiles9

Forks1

Mis à jour15 juillet 2026 à 02:18

Explicit-only. Map BACKLOG.md items into roadmap phases, checking issue and decision impacts and surfacing user-owned prioritization without making ambiguous roadmap edits. Do not use for implementation planning.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

conn-castle

conn-castle/agent-layer

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name	schedule-backlog
description	Explicit-only. Map BACKLOG.md items into roadmap phases, checking issue and decision impacts and surfacing user-owned prioritization without making ambiguous roadmap edits. Do not use for implementation planning.

schedule-backlog

Produce one coherent roadmap proposal from backlog evidence. Proposal-only is the default; edit roadmap files only when the user has authorized a clear prioritization and sequence.

Inputs and evidence

Accept an optional focus, target phase, text query, proposal size, new-phase limit, issue-impact preference, or instruction to apply an unambiguous result. Prefer a cohesive reviewable slice and existing incomplete phases when they fit. Never renumber completed phases.

Read ROADMAP.md, DECISIONS.md, BACKLOG.md, ISSUES.md, and README.md as relevant. Do not invent requirements or implement scheduled work. Keep engineering defects and refactors in ISSUES.md unless the roadmap genuinely needs an engineering phase.

Workflow

Select one cohesive slice using the user's focus, roadmap direction, priorities, dependencies, and shared outcome. Identify duplicates and items that belong in ISSUES.md.
Cross-check prerequisite or obsoleted issues, relevant decisions, and roadmap sequencing constraints.
Propose an existing or new target phase for each group, with rationale, prerequisites, impacts, and—when new—the phase placement, goal, high-level tasks, and exit criteria.
Present alternatives only for a substantive user-owned tradeoff, with pros, cons, and a recommendation. Routine placement within established direction does not require a checkpoint.
In proposal-only mode, return the proposal without edits. When application is already authorized and unambiguous, update ROADMAP.md, BACKLOG.md, and ISSUES.md once so each item has one canonical location. Otherwise leave files unchanged and return the smallest prioritization decision needed.

Return placement, rationale, prerequisites, issue impacts, backlog hygiene, applied changes, and any decision still requiring approval. Use None for an empty category.

Plus depuis ce dépôt

même dépôt

auto-skill-loop

conn-castle/agent-layer

Explicit-only. Run a named autonomous mode, repeatedly selecting, implementing, and shipping coherent work while preserving anything blocked.

2026-08-019

playwright

conn-castle/agent-layer

Use globally installed `playwright-cli` for browser automation, UI inspection, screenshots, Playwright test debugging, or test generation. Trigger when a task needs browser interaction or test repair. Do not use for generic tests, web search, non-browser docs, or API-only work.

2026-07-319

full-workflow

conn-castle/agent-layer

Explicit-only. Align a feature specification, produce a reviewed plan, complete the local work, and ship the pull request.

2026-07-319

review-plan

conn-castle/agent-layer

Explicit-only. Review a plan/task/context artifact set and report material findings.

2026-07-319

ship-pr

conn-castle/agent-layer

Explicit-only. Ship one pull request, observe hosted CI and review feedback, follow PR policy, reply to every eligible comment, and request merge authorization before merging and cleaning up.

2026-07-319

verify-work

conn-castle/agent-layer

Explicit-only. Verify completed work against its authoritative contract and report coverage, working-code evidence, material gaps, and the completion verdict.

2026-07-319

schedule-backlog

Produce one coherent roadmap proposal from backlog evidence. Proposal-only is the default; edit roadmap files only when the user has authorized a clear prioritization and sequence.

Inputs and evidence

Workflow

Select one cohesive slice using the user's focus, roadmap direction, priorities, dependencies, and shared outcome. Identify duplicates and items that belong in ISSUES.md.

Cross-check prerequisite or obsoleted issues, relevant decisions, and roadmap sequencing constraints.

Propose an existing or new target phase for each group, with rationale, prerequisites, impacts, and—when new—the phase placement, goal, high-level tasks, and exit criteria.

Present alternatives only for a substantive user-owned tradeoff, with pros, cons, and a recommendation. Routine placement within established direction does not require a checkpoint.

In proposal-only mode, return the proposal without edits. When application is already authorized and unambiguous, update ROADMAP.md, BACKLOG.md, and ISSUES.md once so each item has one canonical location. Otherwise leave files unchanged and return the smallest prioritization decision needed.

Return placement, rationale, prerequisites, issue impacts, backlog hygiene, applied changes, and any decision still requiring approval. Use None for an empty category.