Setup

Configure the project only after an explicit user request. Discussing, implementing, or reviewing this skill does not invoke it. If it was loaded without a setup request, return to the user's task without changing instructions or starting an interview.

Setup is optional. The other skills provide defaults without it.

Learn the project

1. Identify the target directory from the request or current context. Clarify it only if ambiguous.
2. Read existing project instructions and relevant documentation when accessible. Inspect enough of the directory to understand its purpose, organization, and known commands. The directory need not contain code or Git.
3. Separate observed facts, explicit preferences, and open choices. Follow existing conventions unless the user wants to change them.
4. Check current capabilities and permissions only as needed to carry out setup. Do not save today's tool availability as a permanent project constraint.

When files are inaccessible, use the context the user supplies and return a proposed instruction file as text. State what you could not inspect.

Resolve preferences

Use the interview skill if available, or ask directly. Ask only about choices whose answers materially affect future work. Use short rounds, recommendations with reasons, and more discovery when the topic needs it. Do not require answers to a fixed questionnaire.