Use when work spans many turns or phases and you need durable notes, active-objective tracking, or context compaction without letting stale memory override the current codebase.
EnglishUse when executing a multi-step repository task in phases, especially when progress should be tracked with gates, approvals, retries, localized replanning, or optional subagent delegation instead of one long monolithic run.
EnglishUse when a saved implementation plan should be adversarially reviewed before coding, especially for small, medium, or large tasks that may contain architecture flaws, scope gaps, destructive risk, weak rollback, weak tests, or dependency conflicts.
EnglishUse before planning non-trivial Codex work when the requirements, acceptance criteria, boundaries, constraints, or success measures are not yet clear enough for a safe implementation plan.
EnglishUse when you want the full ControlFlow process as one strict workflow, especially for non-trivial repository work that should move from saved plan to plan review to execution to code review with durable artifacts at each step.
EnglishUse after a ControlFlow plan is saved and before implementation. Runs tier-gated adversarial verification inline: structural audit, assumption/mirage detection, and cold-start executability simulation.
EnglishIncludes Controlflow Memory Hygiene, Controlflow Orchestration, Controlflow Plan Audit, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Controlflow Memory Hygiene
Use when work spans many turns or phases and you need durable notes, active-objective tracking, or context compaction without letting stale memory override the current codebase.
Controlflow Orchestration
Use when executing a multi-step repository task in phases, especially when progress should be tracked with gates, approvals, retries, localized replanning, or optional subagent delegation instead of one long monolithic run.
Controlflow Plan Audit
Use when a saved implementation plan should be adversarially reviewed before coding, especially for small, medium, or large tasks that may contain architecture flaws, scope gaps, destructive risk, weak rollback, weak tests, or dependency conflicts.
Controlflow Spec
Use before planning non-trivial Codex work when the requirements, acceptance criteria, boundaries, constraints, or success measures are not yet clear enough for a safe implementation plan.
Controlflow Strict Workflow
Use when you want the full ControlFlow process as one strict workflow, especially for non-trivial repository work that should move from saved plan to plan review to execution to code review with durable artifacts at each step.
Controlflow Verify
Use after a ControlFlow plan is saved and before implementation. Runs tier-gated adversarial verification inline: structural audit, assumption/mirage detection, and cold-start executability simulation.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Controlflow Memory Hygiene skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.