How do I install the Plan Grooming Idea Briefs skill?

Run npx skillmds add wahidyankf/plan-grooming-idea-briefs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Plan Grooming Idea Briefs safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plan Grooming Idea Briefs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Plan Grooming Idea Briefs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Plan Grooming Idea Briefs?

wahidyankf (@wahidyankf) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plan Grooming Idea Briefs by wahidyankf

Name: Plan Grooming Idea Briefs
Rating: 4.2 (5 reviews)
Author: wahidyankf

Plan Grooming Idea Briefs

Invocable entry point for the plan-ideas-grooming workflow — sweeps one or more repos' plans/ideas/ folders and converges them into a deduplicated, Eisenhower-quadrant-organized, correctly-resident set of two-pagers. Carries the ten-step procedure, the three residency rules (secrets-bearing, single-repo-only, generalizable), the two classification rubrics (urgency, importance), the fail-safe-toward-duplication relocation sequence, and the six-clause termination audit. Use when a repo's flat idea count exceeds 60, when 90 days have elapsed since the last recorded run, or when a maintainer asks for idea grooming across repos.

wahidyankf a4d78ad 5 files · 9.0 KB Updated Sep 10, 2026

File contents

Grooming Idea Briefs

Purpose

This Skill is the invocable entry point for the plan-ideas-grooming workflow. That workflow declares Execution Mode: Direct Orchestration and states that "the procedure lives entirely in this workflow document" — meaning the calling context performs the steps itself and there is no delegated agent behind it. This Skill exists so that running the workflow is a named, callable action rather than an undifferentiated sequence of file edits: invoking it loads the procedure below, and the run is attributable.

Read the workflow document for the full normative text. This Skill carries the operational essentials and the traps; it does not restate all ten steps verbatim.

When to use this Skill

A repo's plans/ideas/ (summed across quadrant folders, excluding README.md) exceeds 60 flat idea files.
90 days have elapsed since the > Last groomed: YYYY-MM-DD line in that repo's plans/ideas/README.md.
A maintainer explicitly asks for idea grooming across one or more repos.

Do not use it to file a new idea (write the two-pager directly) or to promote a ripe idea into a backlog plan (that is plan-idea-promotion-planning).

Inputs

Input	Required	Default	Notes
`repos`	yes	none	Comma-separated repo paths. Supply every repo in one run — Steps 3-4 are cross-repo.
`dry-run`	no	`false`	Compute and log every decision without writing.
`delivery-mode`	no	`worktree-to-pr`	Fixed, no override — write scope below is never infra-as-code.

Hard scope boundary

Write scope is strictly plans/ideas/**, plus Step 9's sanctioned rewriting of inbound links elsewhere. Never create, move, or write under plans/backlog/ or plans/in-progress/, and never promote an idea to a plan. If a step needs to write outside that scope, log it as a follow-up in the grooming log instead.

Procedure

See Procedure for the workflow's ten ordered steps (inventory, within/cross-repo dedup, residency rules R1-R3, fail-safe relocation, reshape, provenance, classify, link rewrite, recurrence-trigger stamp).

Traps and Termination Audit

See Traps and Termination Audit for the five traps this Skill exists to prevent and the six-clause termination audit to run before declaring a grooming run complete.

plan-ideas-grooming workflow — the normative procedure.
Ideas Folder (Two-Pagers) convention — the template every survivor is reshaped against.
plan-idea-promotion-planning — promotes a groomed idea to a plan; this Skill never does.

---name: plan-grooming-idea-briefsdescription: Invocable entry point for the plan-ideas-grooming workflow — sweeps one or more repos' plans/ideas/ folders and converges them into a deduplicated, Eisenhower-quadrant-organized, correctly-resident set of two-pagers. Carries the ten-step procedure, the three residency rules (secrets-bearing, single-repo-only, generalizable), the two classification rubrics (urgency, importance), the fail-safe-toward-duplication relocation sequence, and the six-clause termination audit. Use when a repo's flat idea count exceeds 60, when 90 days have elapsed since the last recorded run, or when a maintainer asks for idea grooming across repos.---# Grooming Idea Briefs## PurposeThis Skill is the **invocable entry point** for the[`plan-ideas-grooming` workflow](../../../repo-governance/workflows/plan/plan-ideas-grooming.md).That workflow declares `Execution Mode: Direct Orchestration` and states that "the procedure livesentirely in this workflow document" — meaning the calling context performs the steps itself andthere is no delegated agent behind it. This Skill exists so that running the workflow is a **named,callable action** rather than an undifferentiated sequence of file edits: invoking it loads theprocedure below, and the run is attributable.**Read the workflow document for the full normative text.** This Skill carries the operationalessentials and the traps; it does not restate all ten steps verbatim.## When to use this Skill- A repo's `plans/ideas/` (summed across quadrant folders, excluding `README.md`) exceeds **60** flat idea files.- **90 days** have elapsed since the `> Last groomed: YYYY-MM-DD` line in that repo's `plans/ideas/README.md`.- A maintainer explicitly asks for idea grooming across one or more repos.Do **not** use it to file a new idea (write the two-pager directly) or to promote a ripe idea into abacklog plan (that is `plan-idea-promotion-planning`).## Inputs| Input | Required | Default | Notes || --------------- | -------- | ---------------- | ------------------------------------------------------------------------------------ || `repos` | yes | none | Comma-separated repo paths. Supply every repo in one run — Steps 3-4 are cross-repo. || `dry-run` | no | `false` | Compute and log every decision without writing. || `delivery-mode` | no | `worktree-to-pr` | Fixed, no override — write scope below is never infra-as-code. |## Hard scope boundaryWrite scope is strictly `plans/ideas/**`, plus Step 9's sanctioned rewriting of inbound linkselsewhere. **Never** create, move, or write under `plans/backlog/` or `plans/in-progress/`, andnever promote an idea to a plan. If a step needs to write outside that scope, log it as a follow-upin the grooming log instead.## ProcedureSee [Procedure](./reference/procedure.md) for the workflow's ten ordered steps (inventory, within/cross-repo dedup, residency rules R1-R3, fail-safe relocation, reshape, provenance, classify, link rewrite, recurrence-trigger stamp).## Traps and Termination AuditSee [Traps and Termination Audit](./reference/traps-and-termination-audit.md) for the five traps this Skill exists to prevent and the six-clause termination audit to run before declaring a grooming run complete.## Related- [`plan-ideas-grooming` workflow](../../../repo-governance/workflows/plan/plan-ideas-grooming.md) — the normative procedure.- [Ideas Folder (Two-Pagers) convention](../../../repo-governance/conventions/structure/plans/ideas-folder-overview-rationale-and-file-layout.md#ideas-folder-two-pagers) — the template every survivor is reshaped against.- [`plan-idea-promotion-planning`](../../../repo-governance/workflows/plan/plan-idea-promotion-planning.md) — promotes a groomed idea to a plan; this Skill never does.

Frequently asked questions