agentleFS
cacardinalcacardinal/laila/.claude/skills/whats-next/SKILL.md

whats-next

Skill1 starsChanged 4 months agoMITView on GitHub

Prioritized 3-5 item recommendation from all sources. Answers "What should I work on?

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use release and handoff.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

Files
SKILL.md

What's Next Skill

Generates a prioritized recommendation of 3-5 actions based on strategy, tasks, reminders, calendar, and goals.

Workflow

  1. Read state/strategy.md — current capacity allocation and priority stack
  2. Query active tasks — state/active-tasks.json plus your task/CRM system (query it here for tasks with status up-next / in-progress, sorted by priority)
  3. Query active initiatives — whatever system holds your Goal -> Initiative -> Task hierarchy, filtered to active, sorted by priority
  4. Query the reminders/task tool — overdue + due today across all lists
  5. Read state/running-brief.json — pending comms items >3 days old
  6. Check the calendar — next 4 hours (protect scheduled time)
  7. Check KPIs/goals — identify any with a downward trend or 0% progress
  8. Apply strategy weighting (percentages come from state/strategy.md, e.g.):
    • Career tasks: 50% weight (primary focus)
    • Health tasks: 20% weight
    • Household/Content: 30% weight
    • Boost items that are overdue or blocking others
    • Demote items that conflict with upcoming calendar events
  9. Output: Numbered list of 3-5 recommended actions:
    Recommended next actions:
    1. [P1/Acme] Resolve the SOW IP clause — blocks the Friday send
    2. [P2/Career] Prep doc for the Verdant Grid discovery call — drives "3 warm pursuits" goal
    3. [P2/Household] Call plumber for water line quote — waiting since Feb 18
    4. [P2/Content] Draft first newsletter post — 0/10 KPI, not started
    5. [P3/Health] Book annual physical — due this month
    Each item includes: priority, domain, action, and which Goal/Initiative/KPI it drives.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.