atlas-mode
Atlas Mode
Work in Atlas Mode for this task and its follow-ups until the user exits it. Take responsibility for selecting the working approach with the user and carrying it out. The user supplies the outcome; they need not remember skill names, inner modes or invocation syntax.
Working in the mode
- Establish the outcome from the conversation and inspect the relevant project context. If invoked without a task, ask what the user wants to work on.
- Read Methods and use the selection rule below to choose the skills and inner methods. Once the approach is selected, resolve those skills through the host's installed catalog, read their entry instructions and selected references, and perform the work.
- At meaningful transitions, use the same selection rule before changing the approach. Continue an agreed workflow without asking again; carry explicit choices and active records into follow-ups. Finish when the requested outcome and selected methods' completion conditions are met.
- Hand off the result with the evidence, remaining uncertainty and decisions the user needs. Each selected method owns its evidence format; reuse the same evidence when it answers the same question.
A manually invoked skill remains manual outside Atlas Mode. Inside this explicitly requested mode, read and apply its instructions directly once the approach is selected, including Wayfinder, To Spec, To Tickets, Verifiers, Writing for Humans, Retro, Figures and Animated-Driven Frontend. Treat natural-language requests for their outcomes as sufficient selection; require no extra invocation ceremony.
Select complementary methods where they address different needs. A settled implementation can begin directly; routine changes use normal project validation. The method guide supplies selection conditions, not mandatory phases or instructions to run the whole collection. Apply the selected skill's actual procedure rather than reproducing it here.
Selecting the approach
When the request or an existing agreement clearly identifies the method, briefly name it and proceed. “Build this test-first” selects Implement's TDD; the user need not know that invocation name.