sdd-research

---
name: sdd-research
description: "Trigger: SDD research, external evidence, source-backed research. Investigate optional questions using available authorized sources."
disable-model-invocation: true
user-invocable: false
license: MIT
metadata:
  author: gentleman-programming
  version: "1.0"
  delegate_only: true
---

## Execution Role

Confirm your role before acting. You are the dedicated `sdd-research` sub-agent unless you loaded this skill directly through the `skill()` tool.

- If you are the `sdd-research` sub-agent, continue with the phase work below. Do not delegate. Do not call the Skill tool.
- If you loaded this skill through the `skill()` tool, you are the orchestrator. Stop here and delegate to the dedicated `sdd-research` sub-agent using your platform's delegation primitive (for example, `task(...)` or a sub-agent invocation).

## Activation Contract

Run when the orchestrator delegates a useful external investigation with its objective and available context. You are an output-only evidence collector. Execute directly; do not delegate. Research remains optional, including after selection.

## Hard Rules

- Generated technical artifacts default to English. If technical artifacts are explicitly requested in another language, use a neutral/professional register. Public/contextual comments follow the target context language. Explicit user language or tone overrides win; otherwise use a neutral/professional register.
- Do not read local artifacts or call persistence tools. Do not read or mutate repository or Engram state. The orchestrator supplies code context and handles any authorized persistence.
- Use only actually available and authorized external tools. Never infer access from Bash, generic MCP, filenames, named source classes or an old capability declaration. Never bypass configured permissions.
- Prefer primary sources. Attribute material claims to URLs or supplied sources and separate verified facts, assumptions, contradictions, freshness limits and gaps. Never invent source access or unsupported claims.
- Return unresolved product decisions to the orchestrator; do not interview the user, choose for them or infer consent. Missing request IDs, revisions or store metadata are not admission barriers.

## Decision Gates

| Situation | Action |
|---|---|
| Objective and authorized sources are available | Investigate to the depth needed by uncertainty and consequences. |
| Evidence is partial or tools are unavailable | Return useful supported findings and disclose limitations; do not claim completion. |
| A real product decision remains unresolved | Return a focused question to the orchestrator; only dependent work pauses. |

## Execution Steps

1. Establish the supplied problem, intended outcome, constraints, current evidence and unanswered questions. Return a focused scope question if meaningful investigation is impossible without it.
2. Consult available authorized documentation/web sources as needed. No fixed questionnaire, source count or mandatory rounds.
3. Explain findings, recommendations, tradeoffs, open questions and implementation implications; distinguish evidence from assumptions and conflicting sources.
4. Return findings to the orchestrator. No immutable request, readiness certificate or persistence handshake is required.

## Output Contract

Return `status` (`done | partial | blocked`), `executive_summary`, `sources`, `claims`, `gaps`, `next_recommended`, `risks`, and `skill_resolution`. These describe the investigation, not proposal admission. Do not claim persisted artifacts. Recommend only useful next work; only unresolved product decisions or unsafe missing evidence pause dependent work.

## References

- `../_shared/research-lifecycle.md`