Wrapper 001
Initial ICP-to-market-validation sequence
A portable wrapper prompt that infers a codebase-supported ICP, audits its market, and prepares a 30-day validation sprint while preserving earlier artifacts.
Ready-to-use prompt
Copy the sequence.
You are working inside a complete product repository.
Read every applicable AGENTS.md file and repository instruction first. Then read and execute the complete canonical prompts at the following URLs, in this exact order:
1. Identify the codebase-supported ICP:
https://grnmn.com/prompts/icp-v0-1-inferred-from-codebase/
2. Audit the market for that ICP:
https://grnmn.com/prompts/initial-icp-market-audit/
3. Prepare the initial market-validation sprint:
https://grnmn.com/prompts/initial-icp-market-validation-sprint/
Treat the instructions at each URL as authoritative and complete. Do not merely summarize them.
Finish and verify each stage before starting the next. Preserve every earlier deliverable. Do not modify application code, access secrets or unauthorized data, invent customer or market evidence, conduct outreach, run pilots, or claim that the market has been validated. Use current external research only where the canonical prompts permit it.
If a URL cannot be accessed or a required stage cannot be completed safely, stop and report the exact blocker. Do not invent substitute instructions or evidence.
At the end, validate all YAML and CSV artifacts and report:
- every file created or updated
- the selected ICP and beachhead
- the market-audit decision
- the strongest unresolved assumptions
- product- and pilot-readiness status
- the exact first execution gate
- the founder's next three actions
Do not describe the resulting ICP or market as validated unless the required customer behavior has actually been observed.Expected result
Decision-ready evidence, not manufactured certainty.
The finished work separates observed evidence, derived judgment, assumptions, and the next commitment-bearing test.
Use this when
Use this when a complete product repository is ready for the full first-pass sequence: infer the strongest codebase-supported ICP, test the size and reachability of its market, and prepare a founder-led validation sprint without manufacturing customer evidence.
Prompts in this wrapper
Run these canonical prompts in order. Their instructions and canonical locations remain independently maintainable; this wrapper supplies the sequence and execution guardrails.
What it produces
- A codebase-supported ICP and narrow initial beachhead
- A bottom-up market audit and traceable prospect universe
- A pre-registered 30-day market-validation sprint
- A consolidated handoff with unresolved assumptions, readiness status, execution gate, and founder actions
Guardrails
- Runs and verifies each canonical prompt in order
- Preserves every earlier deliverable before starting the next stage
- Does not modify application code, access unauthorized data, conduct outreach, or run pilots
- Never presents an ICP or market as validated without observed customer behavior