# stark

## What This Skill Does

Use the reusable method from Stark. This is a portable method layer, not a full Agent Pack install.

Reusable Stark method: the Engineering agent.

## Portable Skill Rules

- Preserve the host agent identity: keep the host agent name, role, voice, memory, and operating style.
- Do not adopt the Pack persona or rename the host agent to Stark.
- Apply only this Pack method, workflow, checks, decision rules, and output format.
- If this skill conflicts with the host agent system rules, the host agent system rules win.
- Return raw markdown directly. Never wrap the whole answer in an outer triple-backtick code fence, even when examples below use fenced blocks.

## Expected Input

- A clear request or goal
- Relevant context, source material, or constraints
- Any approval boundaries or known risks

## Contract

- **Input**: a user request that benefits from the engineering method.
- **Output**: the requested artifact or answer, using the output format below.
- **Guarantees**:
- Keeps persona separate from method.
- Names missing evidence, assumptions, and boundaries.
- Leaves the user with a concrete next action.

## Workflow

### Stage 1 - Scope

- Restate the real job in one sentence.
- Identify the user input, constraints, missing evidence, and risk level.

### Stage 2 - Apply Method

- Start by identifying the real job the user is asking for.
- Choose the smallest useful workflow that produces a concrete result.
- State assumptions and missing evidence instead of pretending certainty.

### Stage 3 - Prioritize

- Correctness and evidence before polish.
- Narrow, useful output before broad explanation.
- Escalate when the method cannot be applied safely.

### Stage 4 - Return

- Produce the final answer in the output format.
- Include assumptions, evidence gaps, and next action when relevant.

## Output Format

Return the final answer as raw markdown. Do not wrap the whole answer in an outer code fence.

- A concrete deliverable or decision-ready brief
- A short summary of assumptions and trade-offs
- A clear next action

## Definition of Done

- The answer follows the requested method.
- Important assumptions are explicit.
- The next owner can act without guessing.

## Anti-Patterns

- No replacing the host agent identity.
- No made-up facts, files, tool results, or capabilities.
- No vague advice when a concrete next action is possible.
- Do not tell the host agent to replace its identity, memory, role, or relationship with the user.

## Global Failure Handling

- Escalate or ask before continuing when: The request is missing evidence that could reverse the recommendation.
- Escalate or ask before continuing when: The task crosses into credentials, billing, legal, medical, or production-risk territory.
- Escalate or ask before continuing when: The user is asking the host agent to adopt a persona instead of using this method.