agentleFS
Sign inStart free
proffesor-for-testingproffesor-for-testing/agentic-qe/.agents/skills/aqe-plan-work/SKILL.md

aqe-plan-work

Skill515 starsChanged 22 days agoMITView on GitHub

Build dependency-aware execution plans for complex Agentic QE, Ruflo, integration, migration, or multi-stream engineering programs. Use when Codex must turn research or requirements into phased work, select a small AQE fleet, map critical paths and parallel streams, define acceptance gates, or sequence risky changes. Use aqe-plan-quality instead when the primary output is only a test or quality plan.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Read AGENTS.md, the objective, relevant research, affected implementation, tests, configuration, and public boundaries.

    line 8
  2. Distinctive:

    Use Ruflo for persistent memory, learned routing, hooks, or multi-agent coordination only when its operational benefit exceeds its setup …

    line 28
  3. Distinctive:

    Treat Claude agent definitions as domain references.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Plan AQE Work

  1. Read AGENTS.md, the objective, relevant research, affected implementation, tests, configuration, and public boundaries.
  2. Define observable outcomes, non-goals, constraints, assumptions, and decisions that require human approval.
  3. Decompose work into independently verifiable deliverables. Map dependencies, consumers, migrations, compatibility boundaries, and rollback points.
  4. Select the smallest useful specialist fleet with references/planning-framework.md. Give every selected specialty a concrete output; do not summon the whole fleet.
  5. Arrange phases so contracts, safety controls, and durable tests precede or accompany implementation. Check CLI/MCP and Claude/Codex parity when shared capabilities cross those surfaces.
  6. Identify work that can run in parallel and a clear critical path. Do not use unsupported precision for time estimates; size work by risk and dependency.
  7. Attach acceptance criteria and the narrowest verification command to each deliverable. Include security, resilience, performance, accessibility, or data-integrity gates only when triggered by the actual scope.
  8. End with prioritized milestones, risks and mitigations, open decisions, and a recommended first vertical slice.

Use Ruflo for persistent memory, learned routing, hooks, or multi-agent coordination only when its operational benefit exceeds its setup overhead. Treat Claude agent definitions as domain references; translate their workflows into available Codex actions rather than copying Claude-only tool syntax.

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.

Reviews can't be read right now.

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