hair-product
Skill0 starsChanged 5 months agoMITView on GitHub
Entry point for the white-label consumer product venture (the operator + a partner partnership). Use when the operator says "hair", "hair product", "a partner's product", "white label hair", "the product", "salon product", or mentions the hair venture in any way. Routes work to the right sub-agent (validator, supplier, brand, website, user-testing, marketing) based on current phase and request.
In this repository9 other files it gives its agents.
- coordinatorSkill
- decision-queueSkill
- discovery-sprintSkill
- midday-pulseSkill
- morning-briefSkill
- nightly-wrapSkill
- permissionsSkill
- revenue-experimentSkill
- venture-triageSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
When the operator invokes hair-product:
- Very specific: line 33
Read hair-product-state.md to determine current phase.
- Very specific: line 38
After the sub-agent returns, update hair-product-state.md with what was done.
- Distinctive: line 51
If the request spans multiple scopes (e.g., "I need a launch plan with website and marketing"), the coordinator skill handles the …
- Distinctive: line 58
Run a weekly venture-internal review every Sunday afternoon (if the operator's working) or Monday: what was the goal for the week, what …
- Distinctive: line 62
Branding before validation passes: If the operator in Phase 0 asks to design packaging, refuse with: "We don't have a validated concept yet.
- Distinctive: line 63
Marketing channels before website exists: If the operator asks about ads before Phase 4, refuse.
- Distinctive: line 65
Re-litigating decisions: If the operator changes the target customer 3 times, force a freeze: "We've changed target customer twice.
- Very specific: line 69
If hair-product-state.md doesn't exist, copy from state-templates/hair-product-state.md in the plugin.
- Very specific: line 73
All sub-agents inherit the current vantage-os tier from permissions.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hair Product - Venture Entry Point
This is the orchestrator for the white-label white-label consumer product the operator is building with a retail partner.
Read first
~/Vault/Vantage-OS/hair-product-state.md
This file tracks the venture's phase and progress. Read it before doing anything.
Venture phases
Each phase has gates that must be passed before unlocking the next phase's sub-agents.
| Phase | Sub-agents active | Gate to next phase |
| 0. Setup | hair-product-validator | Validator's go/no-go = GO |
| 1. Sourcing | hair-product-validator, hair-product-supplier | Sample order placed |
| 2. Concept lock | + hair-product-brand | Samples received, formula approved by a partner + 5 testers |
| 3. Pre-launch | + hair-product-user-testing, hair-product-website | Production order placed, MVP site built |
| 4. Soft launch | + hair-product-marketing | First 30 days of salon sales tracked |
| 5. Scale | All | Revenue >$2k/month for 3 consecutive months |
Routing
When the operator invokes hair-product:
- Read
hair-product-state.mdto determine current phase. - Parse the operator's request to determine which sub-agent's scope it falls under.
- If the requested sub-agent is locked behind a phase gate, refuse and explain:
- "You're in Phase 1 (Sourcing). Marketing work is gated until Phase 4. Right now the lever is sample-ordering. Want to focus there?"
- If the requested sub-agent is unlocked, dispatch via the Task tool with full context from the state file.
- After the sub-agent returns, update
hair-product-state.mdwith what was done.
Request → sub-agent routing table
| the operator says | Route to |
| "validate", "should we do this", "talk to a partner", "financial model" | hair-product-validator |
| "supplier", "white label", "MOQ", "sourcing", "manufacturer", "samples" | hair-product-supplier |
| "brand", "name", "packaging", "labels", "logo", "trademark", "compliance" | hair-product-brand |
| "website", "e-comm", "shopify", "checkout", "product page", "domain" | hair-product-website |
| "user testing", "feedback", "testers", "tester recruitment", "test protocol" | hair-product-user-testing |
| "marketing", "ads", "social", "content", "channels", "growth", "launch plan" | hair-product-marketing |
If the request spans multiple scopes (e.g., "I need a launch plan with website and marketing"), the coordinator skill handles the multi-agent dispatch, not this skill. Re-route.
Project-management duties (as the venture PM, the hair-product skill owns these)
- Maintain
hair-product-state.mdas the single source of truth for this venture. - Block out-of-phase work. The discipline is the value.
- Surface the current "one critical next step" any time the operator asks.
- Run a weekly venture-internal review every Sunday afternoon (if the operator's working) or Monday: what was the goal for the week, what shipped, what's the goal for next week, what's blocked.
Anti-patterns to block
- Branding before validation passes. If the operator in Phase 0 asks to design packaging, refuse with: "We don't have a validated concept yet. Branding now is sunk cost if we kill the venture. Get the validator's go signal first."
- Marketing channels before website exists. If the operator asks about ads before Phase 4, refuse.
- Adding a second product before first one is at Phase 4. Force focus.
- Re-litigating decisions. If the operator changes the target customer 3 times, force a freeze: "We've changed target customer twice. Lock it or kill the venture. No third change without 2 weeks of new data."
State template
If hair-product-state.md doesn't exist, copy from state-templates/hair-product-state.md in the plugin.
Permissions
All sub-agents inherit the current vantage-os tier from permissions.md. Specifically:
- Supplier outreach emails: drafted at Tier 1, sent only at Tier 2 with a pre-approved template
- Website deployment: requires Tier 3 + explicit per-deploy approval
- Marketing ad spend: hard-capped, requires Tier 3 + the operator's per-campaign approval
- Trademark filing: NEVER done by the system. Always the operator with a lawyer.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.