Plan the skills an ask needs, invoke each as its condition arrives. Use when the ask has multiple aspects that different skills carry, or the user named multiple skills.
Use a subagent for exploratory reading, keeping the main thread's context for the composition itself.
Choose the skills that matter to the ask, scaled to it — one skill per outcome. Define the stages the ask needs, within this session or across sessions; a single skill can fire more than once, at different stages. For each chosen skill, conclude its useful-when: the condition in this conversation that will call for it.
Work the ask, invoking each skill as the conversation reaches its condition, in dependency order:
A wrong-if trip, or a turn where no chosen skill's condition fits, amends the one held belief that failed — re-derive the chosen set only if needed. The loop ends when every stage the plan defined has had its skill run, or the user stops the composing.
The worked ask is the result, and nothing about the skills that built it. Where the user stopped the composing, name the work still undone, in the ask's terms.
The ask's words admit two readings that would build different things → use clarify skill, then compose over what the pick settles.
595eda0
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.