review-proposals

Featured

Triages pending improvement-proposal MCP items — presents each with its scope and evidence, collects an accept/reject/defer decision per proposal, and carries out the disposition: project-scoped acceptances get their exact YAML applied to .taskorchestrator/config.yaml and pushed per-root; global acceptances get a tracked GitHub issue (or dwell in review for the maintainer); rejections are recorded and cancelled; deferrals are recorded and left in queue. Use when a user says: review proposals, triage proposals, pending proposals, what proposals are open, adopt proposals, process improvement proposals, accept or reject proposals.

Code & Development 201 stars 21 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
77
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Review Proposals Triages `improvement-proposal` MCP items created by `/session-retrospective` when a cross-session trend graduates. Presents pending proposals, collects a per-proposal decision, and carries out the disposition — including applying project-scoped config changes and filing/linking GitHub issues for global changes. Shared GitHub conventions (issue template, scrub rule, `gh` guard, dedup procedure) are **not** duplicated here — see `<skill-base-dir>/../session-retrospective/references/github-feedback.md` for the full C2/C4/C5 contract and dedup steps referenced throughout Step 5. --- ## Step 0 — Parse Arguments and Read Config Parse `$ARGUMENTS`: - **A UUID** → single-proposal mode: skip Step 1 discovery entirely: go straight to Step 2 for that one item. - **`--scope global` or `--scope project`** → filter Step 1 discovery to only that scope's query. Absent → run both discovery queries. - Neither → full discovery, both scopes. Read the workspace `.taskorchestrator/config.yaml` directly (file read, not MCP) for: - `project.rootId` / `project.name` — enables the project-scoped discovery query and per-root push in Step 5. If absent, project-scoped discovery and project-scoped acceptance are unavailable — proceed with global-only discovery. - `retrospective.github_feedback.enabled` — default `false` if the block or key is absent. - `retrospective.github_feedback.repo` — default `jpicklyk/task-orchestrator` if absent. --- ## Step 1 — Discovery **Sk...

Details

Author
jpicklyk
Repository
jpicklyk/task-orchestrator
Created
1 years ago
Last Updated
2 weeks ago
Language
Kotlin
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category