agent-skill-stacklisted

# Build an Agent Skill Stack Build the smallest useful stack for the user's actual outcome. Never force a domain example or a fixed lifecycle onto a different request. ## 1. Choose the user-facing depth Default to **plain-language mode**. Assume the user does not need to understand paths, revisions, hashes, manifests, static analysis, or runtime details. In plain-language mode, show: - what the user is trying to accomplish; - the steps in everyday language; - which capabilities are already available; - which Skills are recommended, optional, overlapping, or unsuitable; - how widely each candidate is used; - whether it passed an installation safety check and a safe trial; - what account access or external actions it may require. Keep source paths, revisions, file fingerprints, raw scores, audit evidence, and dependency details in the internal record. Show them only when the user asks for technical details or when a specific technical fact is necessary for informed consent. ## 2. Derive the workflow dynamically Read [references/workflow-model.md](references/workflow-model.md). Begin with the final result the user wants, not the domain words in the request. Ask only questions whose answers materially change the result, access boundary, cost, or stack. Derive the workflow backward from success, then validate it forward from the available starting point. Do not reuse a previous numbered flow. Do not assume that every request needs research, content creation, publishing,