# Discovery.tech Landscape

> Assess technical patterns, integrations, and constraints in the domain to inform feasibility and strategy.

- Skill: `majiayu000/discovery-tech-landscape` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/discovery-tech-landscape`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/discovery-tech-landscape/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/discovery-tech-landscape

---


# Purpose
Help engineering leadership quickly synthesize domain research into actionable technical exploration tasks during discovery.

# Pre-run Checklist
- ✅ Align with security, platform, and data stakeholders on non-negotiable constraints.
- ✅ Gather existing architecture diagrams and system inventories.
- ✅ Clarify the decision timeline for selecting technologies.

# Invocation Guidance
```bash
codex skills run discovery.tech_landscape \
  --vars "domain={{domain}}" \
         "constraints={{constraints}}" \
         "existing_stack={{existing_stack}}" \
         "partnership_targets={{partnership_targets}}"
```

# Recommended Input Attachments
- Current architecture diagrams.
- Procurement or compliance requirements.
- Vendor documentation links.

# Claude Workflow Outline
1. Outline the domain context and key constraints.
2. Summarize prevailing architecture patterns, tooling, and best practices.
3. Evaluate integration options, highlighting trade-offs and implementation complexity.
4. Flag high-risk areas requiring spikes or proof-of-concepts.
5. Produce a recommended investigation backlog with owners and timelines.

# Output Template
```
## Domain Overview
...

## Architecture & Pattern Insights
- Trend:
- Impact:

## Integration Considerations
| Option | Benefits | Risks | Effort | Recommendation |
| --- | --- | --- | --- | --- |

## Recommended Spikes
1. Spike Title — Owner (Timeline)
   - Goal:
   - Deliverables:
```

# Follow-up Actions
- Create engineering exploration tickets based on recommended spikes.
- Socialize findings with the product trio to refine scope and timeline.
- Update the architectural decision log once selections are made.