agentleFS
Sign inStart free
websublimewebsublime/mister-anderson/skills/tasks/SKILL.md

tasks

Skill3 starsChanged 7 months agoMITView on GitHub

Create beads from a spec (full decomposition) or from user input (ad-hoc issues). Single entry point for all bead creation.

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use send-user-message, tinyagi-admin and 9 more.

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.
  • Maliot100XSkill

    send-user-message

    Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.

    Also in 4 projects that use this

  • jlia0Skill

    tinyagi-admin

    Manage and operate the TinyAGI system itself — agents, teams, settings, queue, tasks, daemon lifecycle, and source code. Use when the agent needs to: list/add/remove/update agents or teams, check queue status, view logs, start/stop/restart TinyAGI, change settings (provider, model, channels), send messages to the queue, manage tasks, retry dead-letter messages, view recent responses, modify TinyAGI source code or configuration, or perform any administrative operation on the TinyAGI platform. Triggers: 'manage tinyagi', 'add an agent', 'remove a team', 'check queue', 'view logs', 'restart tinyagi', 'change provider', 'update settings', 'create a task', 'modify tinyagi code'.

    Also in 3 projects that use this

  • ArvorCoSkill

    constitution

    Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.

    Also in 4 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 6 projects that use this

  • anyprotoSkill

    skills-manager

    Context-aware routing to skills and hooks management. Use when troubleshooting skill activation, fine-tuning keywords, or managing the automated documentation system.

    Also in 3 projects that use this

  • bivexSkill

    schedule

    Управление расписанием занятий с специалистами по самосовершенствованию. Используй когда пользователь спрашивает о расписании, хочет добавить/удалить/перенести занятие, посмотреть план на день или неделю.

    Also in 4 projects that use this

  • +1 more from ArvorCo

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create epics and issues — either by decomposing a spec or from ad-hoc user input.

    line 9
  2. Distinctive:

    If the user provides $ARGUMENTS, analyze them for:

    line 14
  3. Distinctive:

    Spec must exist and be APPROVED: Ask the user for the spec path.

    line 27
  4. Distinctive:

    PRD must exist: Ask the user for the PRD path.

    line 28
  5. Distinctive:

    Parent epic (optional): Ask if issues should belong to an existing epic.

    line 32
  6. Very specific:

    No spec found. Recommend running /spec first, or switch to ad-hoc mode for individual issues.

    line 36
  7. Very specific:

    No PRD found. Recommend running /requirements first.

    line 40
  8. Distinctive:

    Verify epics and issues were created

    line 79
  9. Very specific:

    Use bd ready to see available work.

    line 88

“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tasks

Create epics and issues — either by decomposing a spec or from ad-hoc user input.

<on-init> If the user provides $ARGUMENTS, analyze them for: - A spec path (full decomposition mode) - A PRD path - An issue description or list (ad-hoc mode) - A parent epic ID

Determine the mode:

  • Full decomposition — user references a spec or PRD to decompose
  • Ad-hoc — user describes individual issues to create</on-init>
<on-check> **Full decomposition mode:** 1. **Spec must exist and be APPROVED.** Ask the user for the spec path. Read to confirm. 2. **PRD must exist.** Ask the user for the PRD path. Read to confirm.

Ad-hoc mode:

  1. Issue context must be provided. Either from user input or referenced documents.
  2. Parent epic (optional). Ask if issues should belong to an existing epic.</on-check>
<on-check-fail if="spec"> No spec found. Recommend running `/spec` first, or switch to ad-hoc mode for individual issues. </on-check-fail><on-check-fail if="prd"> No PRD found. Recommend running `/requirements` first. </on-check-fail><on-execute>

Full Decomposition Mode

Dispatch using exactly these parameters — no more, no less:

Agent(
    subagent_type="beads-owner",
    prompt="Create epics and issues for the requested solution. Product requirements: {prd_path}. Spec: {spec_path}. Read both documents for full context before creating issues. CRITICAL — Reference-only beads: set --spec-id to the PRD document reference. Set --external-ref to the spec path with section references. Set --design to a one-line pointer (e.g., 'See {spec_path} § {section}'). Acceptance criteria must be verifiable pass/fail conditions only — no implementation details. NEVER copy spec content into description or design fields. Tasks define WHAT to do; specs define HOW to do it. Beads track work; specs define work."
)

Do NOT add extra parameters unless the user explicitly requests it.

Ad-hoc Mode

Gather context:

  1. What issue(s) to create? From user input or documents.
  2. Which epic should they belong to? Ask for parent epic ID if applicable.
  3. Any reference documents (PRD, spec, plan)?

Dispatch using exactly these parameters — no more, no less:

Agent(
    subagent_type="beads-owner",
    prompt="Create issues based on the following context. Issue description: {user_input_or_summary}. Reference documents: {doc_paths_if_any}. Parent epic: {epic_id_or_none}. Project type: {monorepo with package X | single-repo}."
)

Do NOT add extra parameters unless the user explicitly requests it.

</on-execute><on-complete> 1. Verify epics and issues were created 2. Show the user a summary: number of epics, total issues, dependency graph </on-complete><on-next> Stage 2 complete. Recommend proceeding to Stage 3: Guided: `/implementation {NN}` — walks through investigate → do → review → quality per task Direct: `/investigate` — jump straight to investigating a task

Use bd ready to see available work. </on-next>

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.

Check your setup, free