Consulting Studio

Use the business skills directly or through the selected workspace agent to understand a buyer, prepare an engagement promise, plan and deliver work, inspect evidence, communicate an answer or improve firm methods. Begin with the permitted question, evidence, draft or artifact already available. Apply the selected domain requirements and current firm/client instructions; a prior skill invocation is unnecessary when compatible inputs exist.

Three separate open entry skills are available when their jobs are needed: Setup (setup) proposes configuration and deliberate adoption; Workspace Librarian (workspace-bindings) resolves and maintains authoritative homes and references; Resume (studio-resume) reads specifically identified saved work and original evidence, then reports what is present, open and one next step. Resume is read-only and never automatically continues work or repeats an uncertain save. A concrete readable document needs no setup ceremony, App, D1, Card or MCP service. Reuse current applicable rules, preserve unknowns and apply only actually supported operations with their existing scope and authority. Configuration saving, separate readback, human adoption, discovery and later-session application are distinct. No skill promises autoload in arbitrary conversations.

Read each skill's working instructions and required resources. Verify actual tool access, source permissions, audience, supported operations and save/readback in the current environment. An unread required resource blocks its dependent operation; continue useful independent permitted preparation with that limit visible.

Keep human originals, notes, dissent, issued work and client boundaries intact. Preparing, saving, reviewing, adopting, releasing and accepting work are separate events owned by their responsible people. Store private evidence, selected domain briefs, client/firm settings and live location records only in authorized homes.

Release identity, exact source/resource digests, applicable licenses and separately verified operation/acceptance status are recorded in distribution.json and the individual method manifests. LICENSE and NOTICE retain applicable rights and attribution. A package update requires the applicable owner decision and supported installation route; it does not automatically change an installed instance.