agentleFS
Sign inStart free
Golden-PromiseGolden-Promise/codex-skill-library/skills/skill-subtask-context/SKILL.md

skill-subtask-context

Skill1 starsChanged 8 months agoMITView on GitHub

Use when a bounded child task needs its own local context, scope, and restart state without inflating the root task summary.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this package when a long-running task needs a child task with its own local state.

    line 10
  2. Distinctive:

    Keep the package boundary narrow: open, refresh, or close subtask state without taking over root state, packet compression, workflow gates, …

    line 11

≈ “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.

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

Skill Subtask Context

Overview

Use this package when a long-running task needs a child task with its own local state. Keep the package boundary narrow: open, refresh, or close subtask state without taking over root state, packet compression, workflow gates, or final handoffs.

Use This Skill When

  • a child task needs its own .agent-state/subtasks/<slug>/TASK_STATE.md
  • the parent task is getting noisy and should hand a bounded slice to a separate owner
  • a subtask needs local facts, local risks, and local exit criteria
  • a child task is closing and its merge notes need to be made explicit

Do Not Use This Skill When

  • the root task state itself needs a refresh
  • the next step only needs a compressed packet rather than a full local state refresh
  • the task needs a risky-change checkpoint or formal gate
  • the task is pausing and needs a handoff summary instead of active subtask state

Package Boundary

This package owns local child-task state such as .agent-state/subtasks/<slug>/TASK_STATE.md. It does not own root task state, does not own packet compression, does not own workflow gates, and does not own final handoffs.

References

  • README.md and README.zh-CN.md: entry docs and direct invocation wording
  • references/use-cases.md: positive and negative trigger examples
  • references/prompt-templates.en.md: reusable prompt patterns
  • assets/TASK_STATE.template.md: subtask-state template

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