next-advisor
Skill13 starsChanged 5 months agoMITView on GitHub
Diagnoses the initiative state and recommends the 1-3 most valuable next actions. Use when the PM says "what's next", "что дальше", "continue", "где мы", "продолжаем", "what should I do", or seems unsure where to go — instead of mechanically suggesting the next pipeline step number.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ambiguity-resolverSkill
- challengeSkill
- deep-thinkSkill
- design-critique-templateSkill
- experiment-designSkill
- ingestSkill
- interview-analysisSkill
- multi-source-signal-synthesiserSkill
- pipeline-stepsSkill
- post-launch-reviewSkill
- problem-structuringSkill
- product-requirements-docSkill
- setup-initiativeSkill
- solution-scoringSkill
- strategic-narrative-generatorSkill
- system-design-docSkill
- technical-spec-documentSkill
- tracking-and-funnelsSkill
- ui-pattern-librarySkill
- user-persona-builderSkill
- user-story-generatorSkill
- user-testingSkill
The file
Files
Next Advisor — /next
Recommend the most valuable next action from state, not from step numbers. "You are on step 6, next is step 7" is exactly what this skill replaces.
Inputs (read all that exist)
output/hypotheses.json— the registry (orhypotheses.py show <dir>)python3 tools/scripts/validate-evidence.py <dir>— violationspython3 tools/scripts/coverage.py <dir>— phase map + focusoutput/status.json—dependencies[](ages, deadlines, blocks; legacypending.*values count too) andstepsstatuses- Last 2-3 entries of
output/decisions.md— what was promised last time CONTEXT.md— is there a target? kill criteria?
Diagnosis order (first match wins the top slot; report up to 3)
- Stalled external dependency — an entry in
dependencies[]past its deadline (or a legacy pending older than 7 days — legacy support ends in 2.0) → recommend: chase the owner / move the deadline / switch to synthetic (downgrading dependent hypotheses) / consciously skip (status: "skipped"). Name the blocked hypotheses fromblocks. - Evidence violations — flagged
data_inconsistencyheld above 0.6, confidence outside type range → recommend reconciling before anything built on those numbers (especially before a gate). - Ready-but-unstarted work — e.g. ≥2 hypotheses confirmed REAL and
/solutionsnot run; solutions scored and/sketchempty; deck ready and gate not rehearsed → recommend the job that converts existing evidence into progress. - Frame gaps that now matter — no target/kill criteria AND a gate is
near → recommend
/setup-initiative(this is the only moment to push it). - Open hypotheses without a validation path — testing/draft hypotheses
that no brief or dependency covers → recommend
/briefor/ingest.
Output format
Short. For each recommendation: what → why now → one command/action to start. Reference hypothesis ids and real dates/ages. No generic advice ("keep validating") — every line must be executable today. If everything is genuinely blocked on external people, say exactly that and list who owes what since when.
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.

