sponsor-questions-walkthrough
Skill1 starsChanged 6 months agoNo licenceView on GitHub
Walk the sponsor through accumulated open orchestrator-side decisions one at a time, using AskUserQuestion popups with concrete options + per-option descriptions so the sponsor can click instead of typing freeform answers. Use whenever the sponsor says "sponsor questions walkthrough", "/sponsor-questions-walkthrough", "sponsor gate questions", "/sponsor-gate-questions", "walk me through your questions", "what do you need from me", "what are your open questions", "any open questions", "any gates you need me for", "what gates need my approval", "go through your questions", or otherwise asks for a structured pass through pending sponsor decisions or gate approvals. Questions come from BOTH live-session context (the bulk — decisions the orchestrator deferred during the current session) AND persisted sources (team/STATE.md "pending sponsor" markers, .claude/away-queue.md, .claude/decisions-while-away.md entries with Status: pending review, ClickUp tickets flagged for sponsor). Replaces the freeform-bullet-list pattern with focused one-question-at-a-time popups; surfaces only items that genuinely need sponsor input, never fabricates filler.
In this repository22 other files it gives its agents.
- auto-pixellabSkill
- auto-statusSkill
- clone-sessionSkill
- codereviewSkill
- create-orchestration-projectSkill
- drain-and-save-sessionSkill
- drain-sessionSkill
- grill-meSkill
- investigateSkill
- keep-screens-aliveSkill
- mentor-modeSkill
- pbiSkill
- post-prSkill
- post-releaseSkill
- project-alignment-analysisSkill
- save-sessionSkill
- skill-creatorSkill
- skill-zip-shareSkill
- start-branchSkill
- start-flowSkill
- start-pbiSkill
- start-prSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 18 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.