NIW Case Builder
Use this skill after niw-officer-review or whenever the user wants to turn a weak or messy case into a tighter one.
This is an educational drafting workflow, not legal advice.
Goal
Build a case that is:
- narrower;
- easier to prove;
- less emotionally noisy;
- more legible under
Dhanasar;
- less dependent on unsupported claims.
Build sequence
1. Choose one anchor endeavor
Do not let the case split into multiple companies, missions, or populations unless the user already has unusually strong evidence across all of them.
Prefer one anchor endeavor that best satisfies all three:
- strongest national-importance framing;
- strongest execution proof;
- strongest reason to waive the job offer and labor certification.
2. Write the endeavor statement
Use this format:
The petitioner seeks to advance a U.S.-based endeavor focused on [specific intervention], addressing [specific national problem or system-level gap] by [method], with expected impact on [defined public, industry, or regional outcome].
Avoid:
- visionary language;
- self-brand language;
- broad platform language;
- claims that sound like a mission statement.
3. Build the evidence chain
Map every claim to proof.
Use four buckets:
problem evidence: data, reports, burden, shortage, cost, access gap;
execution evidence: history, product, clients, pilots, grants, publications, patents, partnerships;
outside validation: expert letters, customer letters, media, awards, accelerators, agencies, adoption;
waiver logic: why this work should not be trapped inside one employer relationship.
If a claim has no proof, either weaken it or remove it.
4. Reframe founder stories
Founder stories should sound like public-benefit execution stories, not personal journeys.
Translate:
- from
I care deeply about this issue
- to
I have built a specific mechanism to address a documented U.S. gap.
Translate:
- from
my company will succeed
- to
the proposed endeavor is already being advanced through identifiable steps with outside validation.
5. Draft support letters correctly
Support letters should do at least one of these:
- validate the national problem;
- validate the petitioner’s role and capability;
- validate demand, adoption, or implementation value;
- explain why the work has broader implications beyond one employer.
Letters that only praise intelligence or work ethic are low value.
Output format
Default to:
Reframed case thesis
One paragraph.
Proposed endeavor
One polished paragraph.
Evidence map
Prong 1:
Prong 2:
Prong 3:
Claims to cut
List claims that should be removed or softened.
Evidence to obtain next
Prioritize the highest-value missing pieces.
Drafting notes
State what tone and logic the full petition should follow.
Sector lenses
Women’s health / hormonal health
Prefer frames tied to:
- access to care;
- diagnostic delay;
- patient navigation;
- underserved populations;
- reproductive, endocrine, menopausal, or chronic-condition burden;
- measurable public-health or healthcare-delivery impact.
Be careful with:
- wellness-only positioning;
- consumer-brand language;
- generalized empowerment messaging without clinical or system-level evidence.
Conservation / environmental work
Prefer frames tied to:
- measurable ecological or resilience outcomes;
- public infrastructure, land, water, agriculture, compliance, monitoring, or risk reduction;
- scalable implementation rather than local volunteering.
Be careful with:
- passion-project framing;
- local-only restoration narratives;
- impact claims without policy, data, or deployment pathway.
AI / deep tech
Prefer frames tied to:
- a specific deployed capability with named users, pilots, or integrations;
- national priorities such as critical technology, security, infrastructure, or competitiveness;
- measurable adoption, performance, or cost outcomes.
Be careful with:
- "AI" as a buzzword without a working system behind it;
- hype language borrowed from fundraising decks;
- national-importance claims that rest on the industry’s importance alone.
References
Read these only when needed:
- USCIS and AAO criteria
- Drafting red flags
1---2name: niw-case-builder3description: NIW Case Builder4---56# NIW Case Builder78Use this skill after `niw-officer-review` or whenever the user wants to turn a weak or messy case into a tighter one.9This is an educational drafting workflow, not legal advice.1011## Goal1213Build a case that is:1415- narrower;16- easier to prove;17- less emotionally noisy;18- more legible under `Dhanasar`;19- less dependent on unsupported claims.2021## Build sequence2223### 1. Choose one anchor endeavor2425Do not let the case split into multiple companies, missions, or populations unless the user already has unusually strong evidence across all of them.2627Prefer one anchor endeavor that best satisfies all three:2829- strongest national-importance framing;30- strongest execution proof;31- strongest reason to waive the job offer and labor certification.3233### 2. Write the endeavor statement3435Use this format:3637`The petitioner seeks to advance a U.S.-based endeavor focused on [specific intervention], addressing [specific national problem or system-level gap] by [method], with expected impact on [defined public, industry, or regional outcome].`3839Avoid:4041- visionary language;42- self-brand language;43- broad platform language;44- claims that sound like a mission statement.4546### 3. Build the evidence chain4748Map every claim to proof.4950Use four buckets:5152- `problem evidence`: data, reports, burden, shortage, cost, access gap;53- `execution evidence`: history, product, clients, pilots, grants, publications, patents, partnerships;54- `outside validation`: expert letters, customer letters, media, awards, accelerators, agencies, adoption;55- `waiver logic`: why this work should not be trapped inside one employer relationship.5657If a claim has no proof, either weaken it or remove it.5859### 4. Reframe founder stories6061Founder stories should sound like public-benefit execution stories, not personal journeys.6263Translate:6465- from `I care deeply about this issue`66- to `I have built a specific mechanism to address a documented U.S. gap.`6768Translate:6970- from `my company will succeed`71- to `the proposed endeavor is already being advanced through identifiable steps with outside validation.`7273### 5. Draft support letters correctly7475Support letters should do at least one of these:7677- validate the national problem;78- validate the petitioner’s role and capability;79- validate demand, adoption, or implementation value;80- explain why the work has broader implications beyond one employer.8182Letters that only praise intelligence or work ethic are low value.8384## Output format8586Default to:8788### Reframed case thesis8990One paragraph.9192### Proposed endeavor9394One polished paragraph.9596### Evidence map9798- `Prong 1`:99- `Prong 2`:100- `Prong 3`:101102### Claims to cut103104List claims that should be removed or softened.105106### Evidence to obtain next107108Prioritize the highest-value missing pieces.109110### Drafting notes111112State what tone and logic the full petition should follow.113114## Sector lenses115116### Women’s health / hormonal health117118Prefer frames tied to:119120- access to care;121- diagnostic delay;122- patient navigation;123- underserved populations;124- reproductive, endocrine, menopausal, or chronic-condition burden;125- measurable public-health or healthcare-delivery impact.126127Be careful with:128129- wellness-only positioning;130- consumer-brand language;131- generalized empowerment messaging without clinical or system-level evidence.132133### Conservation / environmental work134135Prefer frames tied to:136137- measurable ecological or resilience outcomes;138- public infrastructure, land, water, agriculture, compliance, monitoring, or risk reduction;139- scalable implementation rather than local volunteering.140141Be careful with:142143- passion-project framing;144- local-only restoration narratives;145- impact claims without policy, data, or deployment pathway.146147### AI / deep tech148149Prefer frames tied to:150151- a specific deployed capability with named users, pilots, or integrations;152- national priorities such as critical technology, security, infrastructure, or competitiveness;153- measurable adoption, performance, or cost outcomes.154155Be careful with:156157- "AI" as a buzzword without a working system behind it;158- hype language borrowed from fundraising decks;159- national-importance claims that rest on the industry’s importance alone.160161## References162163Read these only when needed:164165- [USCIS and AAO criteria](references/uscis_and_aao.md)166- [Drafting red flags](references/drafting_red_flags.md)