Skip to content

hashgraph-online/awesome-codex-plugins / plugins/boshu2/agentops/skills/plan

Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use when: planning, breaking down or scoping a change.

FileKindSize
SKILL.mdskill md10.1 KB
references/challenge.mdmarkdown3.6 KB
references/ground-truth-routing.mdmarkdown5.7 KB
references/resume-and-handoff.mdmarkdown4.3 KB

references/challenge.md

View on GitHub
# Optional challenge

Plan owns this shared method. Load it for consequential uncertainty that
survives the available source checks and relevant observations. Clear tasks
and known repairs proceed directly. Source facts need sources, empirical
unknowns need observations, and caller choices need the caller.

## One bounded exchange

1. Frame the accepted outcome, disputed claim, relevant source pointers and the
   decision at stake. Preserve acceptance and scope unchanged. Use the author's
   proposal plus one fresh challenger by default, with distinct native context
   identity and only the inputs needed for this question. Follow
   [model-dispatch](../../validate/references/model-dispatch.md) for actual
   authorization, same-family default, explicit cross-model selection and real
   remaining bounds. Method selection itself grants no dispatch authority.
   Without it, do not stand in as your own challenger: mark the claim as
   inference and return it with the check that would settle it. A requested
   Premortem instead runs its checks and states that the independence leg is
   missing ([its workflow](../../premortem/SKILL.md#workflow), step 2).
2. The challenger gives the strongest counterexample or contrary evidence,
   identifies the assumption it attacks, and names what would change its view.
   Unsupported possibilities remain hypotheses; seek a concrete defeating
   construction when possible.
3. The author answers once with a source, corrected proposal, bounded probe or
   admitted uncertainty. This is one targeted exchange, not a loop until agents
   agree. A replacement reply context gets the disputed claim, cited evidence
   and question/answer delta only; its reply is not a new independent vote.
4. Stop when a correction resolves the defect, a source settles the fact, a
   caller-owned choice is isolated, a test is the remaining discriminator, no
   useful novelty remains, or the actual limit is reached. Retain disagreement
   when it survives. Further investigation needs a named unanswered question
   and room within existing authority and bounds, never a renewed allowance.

Record the supported decision or unresolved choice, strongest counterevidence,
reason to revise or retain the approach, and next check in the existing intent
or native handoff. Pass this compact delta to the implementer; do not load the
full debate transcript. More extensive evidence is only for a concrete consumer
or requested audit under the existing storage rules.

## Other selected strategies

When independent alternatives themselves matter, two sealed positions may be
selected: both authors get the same accepted question and source evidence, both
initial positions are fixed before comparison as
[Council](../../council/SKILL.md#rules-that-decide-the-synthesis) seals views,
later replies are peer-informed, and a newly found decisive source goes to both
or the unequal evidence is disclosed.
An independent derivation can also be compared with an already fixed proposal.

[Premortem](../../premortem/SKILL.md) owns a requested plan-failure examination,
including evidence shape, reversibility and concrete defeat attempts.
[Council](../../council/SKILL.md) remains a caller-selected broader strategy.
Neither is required for this method. Explicitly required review legs remain
required; a cheaper challenge cannot replace them.

Challenge produces advisory evidence. Agreement is neither caller approval nor
independent confirmation of correctness. It cannot issue acceptance, change
work ownership, admit context, close work or replace fresh author-distinct
Validate over exact content and unchanged acceptance.
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall