How do I install the Aqe Plan Work skill?

Run npx skillmds@latest add proffesor-for-testing/aqe-plan-work in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aqe Plan Work safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aqe Plan Work?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aqe Plan Work free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aqe Plan Work?

proffesor-for-testing (@proffesor-for-testing) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aqe Plan Work by proffesor-for-testing

Name: Aqe Plan Work
Rating: 4.2 (5 reviews)
Author: proffesor-for-testing

Aqe Plan Work

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.

File contents

Plan AQE Work

Read AGENTS.md, the objective, relevant research, affected implementation, tests, configuration, and public boundaries.
Define observable outcomes, non-goals, constraints, assumptions, and decisions that require human approval.
Decompose work into independently verifiable deliverables. Map dependencies, consumers, migrations, compatibility boundaries, and rollback points.
Select the smallest useful specialist fleet with references/planning-framework.md. Give every selected specialty a concrete output; do not summon the whole fleet.
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.
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.
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.
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.

--- name: aqe-plan-work description: 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. --- # 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](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.

Frequently asked questions