القائمة
Integrate Phase 0 and Phase 1A outputs into TAM/SAM/SOM sizing, buyer personas, and market entry signals. Run after `analyzing-source-project` and `researching-industry-landscape` (Phase 1B).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | researching-market |
| description | Integrate Phase 0 and Phase 1A outputs into TAM/SAM/SOM sizing, buyer personas, and market entry signals. Run after `analyzing-source-project` and `researching-industry-landscape` (Phase 1B). |
| compatibility | Designed for Claude Code |
| metadata | {"stability":"development","allowed-tools":"Read, Write, Glob, Grep, WebSearch, WebFetch, Agent","argument-hint":["market-or-product-category"]} |
Target: $ARGUMENTS
Phase 1B of the GTM pipeline. Depends on Phase 0 and Phase 1A. Integrates technical capability and competitive intelligence into strategic market sizing and buyer analysis.
Read config/mode.md before starting:
concise — Top-down TAM estimate, one primary persona, bullet entry signalsdetailed — Bottom-up + top-down sizing, 2-3 personas with full profiles, trend projectionsconservative — Use published analyst figures, conservative growth ratesambitious — Build bottom-up case for expansive TAM, highlight adjacenciesresults/phase-0/capability-profile.md — Source project capabilitiesresults/phase-1a/competitor-map.md — Competitive landscapeconfig/targets.md — Target market segmentsconfig/comments_research.md — Research scope constraintsconfig/mode.md — Style and approach settingsconfig/validation_criteria.md Phase 1B gatesWrite to results/phase-1b/:
market-analysis.md# Market Analysis
## Market Sizing
### TAM (Total Addressable Market)
- Estimate: $[X]B
- Methodology: [top-down / bottom-up]
- Source: [URL, year]
### SAM (Serviceable Addressable Market)
- Estimate: $[X]B
- Scope: [geography, segment, use case]
### SOM (Serviceable Obtainable Market — Year 1-3)
- Estimate: $[X]M
- Assumptions: [list]
## Growth Rate
- [X]% CAGR through [year] — Source: [URL]
## Buyer Personas
### Persona: [Name/Role]
- Title: [job title]
- Pain: [primary pain point]
- Budget authority: [Yes/No/Influence]
- Buying trigger: [what prompts purchase decision]
## Market Entry Signals
- [Signal] — Strength: [High/Medium/Low]
## Risks
- [Risk] — Likelihood: [H/M/L] — Mitigation: [approach]
config/targets.mdVerify an external or AI-generated security report against the actual codebase before acting on it. Use when handed a scanner PDF, automated teardown, audit report, or bug-bounty submission — classifies every finding CONFIRMED / OVERSTATED / FALSE-POSITIVE / FABRICATED and salvages the real work items.
Creates GitHub Actions for the Marketplace. Use when scaffolding a new action, implementing composite steps, writing BATS tests, or preparing a Marketplace release.
Audit documentation against its declared hierarchy — broken links, duplicates, misplaced content, stale references, single-source-of-truth enforcement. Use for doc health reviews.
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
Audits website accessibility for WCAG 2.2 AA compliance, generating findings and code fixes. Use when reviewing accessibility, keyboard navigation, screen reader compatibility, or inclusive design.