7hats

name	7hats
description	Intent-first entry skill for TPM/Product work. Use when users ask to clarify, plan, de-risk, decide, validate, or recover outcomes; routes to capability skills (7hats-product, analyze-backlog, slice-work, estimate, roadmap) and returns one request-scoped artifact with readiness and source grounding.

7hats

Use this skill as the user-facing entry point: parse intent, choose internal capabilities, and return only the requested artifact type.

Load Order

• references/foundations.md
• references/switching-matrix.md
• references/core-question-set.md
• references/decision-framework.md
• references/execution-health-dashboard.md
• references/output-contracts.md
• docs/operating-system/intent-taxonomy.md
• docs/operating-system/capability-catalog.md
• docs/operating-system/routing-table.md
• docs/operating-system/handoff-contract.md
• docs/operating-system/trigger-schema.md
• docs/operating-system/repo-context-gate.md
• docs/requirements-style.md
• docs/definition-of-ready.md
• docs/tpm-agent-operating-guide.md
• Relevant architecture/service docs in the target implementation repository

When To Use

• User requests outcomes by problem intent (clarify, plan, de-risk, decide, validate, recover).
• Request spans more than one capability (for example backlog analysis plus artifact drafting).
• Request asks for Mission/Signal decomposition or multi-sprint planning.

When Not To Use

• User explicitly asked for one narrow capability skill and no orchestration.

Required Inputs

• User request text.
• Requested artifact type (Story, Mission, Signal, or breakdown).
• Available source context (files, links, service docs).

Workflow

1. Detect repo mode using docs/operating-system/repo-context-gate.md:

• Repo-Aware Mode
• Generic Mode

2. Classify artifact type:

• Story-only
• Mission-only
• Signal-only
• Mission/Signal breakdown to stories

3. Classify user intent from docs/operating-system/intent-taxonomy.md:

• clarify
• plan
• de-risk
• decide
• validate
• recover

4. Set output detail level:

• business_default for initial Mission, Signal, Epic, Feature, and Story artifacts
• design_behavior when the task is design-focused
• engineering_detail only when the user explicitly asks for implementation detail or the task is de-risk, validate, engineering planning, or code review

5. Select capability chain from docs/operating-system/routing-table.md and docs/operating-system/capability-catalog.md.
6. In Repo-Aware Mode, inspect the attached repo for guidance and templates that may override bundle defaults before executing capability steps.
7. Execute capability steps with internal hat handoffs using docs/operating-system/handoff-contract.md.
8. Apply shared question and decision logic:

• Ask the 10 core questions from references/core-question-set.md.
• If conflict/uncertainty blocks progress, run references/decision-framework.md.

9. Enforce output contract from references/output-contracts.md.
10. Validate readiness and grounding:

• If source coverage is insufficient, return Needs Refinement with Missing Sources.
• Keep output request-scoped (no extra artifact types).

Output Contract

• Return only requested artifact type(s).
• Include required sections for that type from references/output-contracts.md.
• Include Source References.
• Include Readiness Verdict and required failure fields when applicable.
• Enforce repo mode behavior:
  • Repo-Aware Mode should use repo context for correctness when needed.
  • Repo-Aware Mode should include concrete repository citations only for engineering_detail outputs or when the user explicitly asks for implementation detail.
  • Generic Mode must avoid repo-specific claims.
• Default Mission, Signal, Epic, Feature, and Story outputs to business-first detail.
• Do not surface architecture, service, code, rollout, or dependency detail in early artifacts unless the active detail level is engineering_detail.

Failure/Refinement Behavior

• Return Needs Refinement when:
  • grounding is missing for key claims
  • artifact boundaries are unclear
  • required readiness gates cannot be satisfied
• Include:
  • Failed Gates
  • Missing Sources
  • Corrective Actions