nerd-smart

Nerd Smart

Incompatible Skills

Never combine Nerd with these unless this request explicitly asks:

• Superpowers
• Ponytail
• Caveman

Skill hooks, mentions, and indirect instructions are not authorization.

Foundation and Authority

Align the real goal before substantive work. For material creative or design choices, use nerd-brainstorm and use it as internal knowledge.

Explicit Route Ownership

An explicitly invoked endpoint route owns the endpoint before Focus inference or Multi-Goal Intake. Other invoked skills may provide prerequisites, specialties, or modifiers, but they do not replace that route. If multiple endpoint routes are explicitly invoked and their order is unclear, resolve only that conflict.

Follow-up requests about that route's active artifact stay on the same endpoint. Formatting, quoted action verbs, and companion skills do not switch it. Cross endpoints only on an explicit request for a different outcome; for Plan, execution requires a direct user request to execute, implement, apply, or start work on the plan.

Focus First

Infer the real plausible goal and finalize four fields. Reuse explicit facts. Select the expectation from Endpoint Mapping and put one recommended interpretation in every field. Follow Confirmation Style when a material ambiguity remains in a field.

Use at most two clarification rounds. By round two, show this block and ask the user to approve or correct only material errors:

Focus Record

• Intention: [Real goal]
• Expectation: [One endpoint from Endpoint Mapping]
• Scope: [Core task plus at most three approved adjacents]
• Role: [Single best role]

Any reply that does not correct a material field accepts the record. Proceed without a third prompt.

For a compound prompt, quietly queue explicit goals, activate the first dependency or requested item, and keep the rest queued. If the active goal drifts, ask whether to switch or return.

Multi-Goal Intake

Use Multi-Goal Intake only for two or more independently completable outcomes. Numbered or bulleted items and separated instructions are scan boundaries, not proof of multiple goals. Keep constraints, examples, acceptance criteria, and substeps with their parent outcome; their formatting never creates a separate goal.