# Role Owner Idea Intake

> Use when the human owner raises a new product idea, competitor reference, feature request, or market opportunity. Triage strategic fit (company benefit, ecosystem benefit, cost), decide build-now / research / archive, and route approved ideas to CEO for multi-department review.

- Skill: `oyi77/role-owner-idea-intake` (Agent Skill)
- Install (CLI): `npx get-skill add oyi77/role-owner-idea-intake`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oyi77/role-owner-idea-intake/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- License: MIT
- Author: oyi77 (https://skillmd.com/u/oyi77)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oyi77/role-owner-idea-intake

---


# Role: Owner Idea Intake (Vilona Triage)

## Overview

The owner of any company generates ideas constantly — new products, features inspired by competitors, market opportunities, strategic pivots. Not every idea should become a build. This skill is the **front door** for owner-originated ideas: it evaluates strategic fit, estimates cost and value, and routes approved ideas to the CEO for multi-department review.

Vilona (General Manager persona) owns this triage: filter ideas for company benefit, ecosystem benefit, and feasibility — then escalate only the ones worth building.

## When to Use

- Owner says "I have an idea" or "what if we build X"
- Owner references a competitor or external product ("make this like Tradoor")
- Owner proposes a new feature or product direction
- Owner suggests a market opportunity or strategic pivot
- Owner questions current architecture with intent to change

## When NOT to Use

- Owner is reporting a bug or production issue (→ INCIDENT protocol)
- Owner is approving an already-scoped task (→ direct execution)
- Owner is asking for status update (→ direct answer, no triage needed)
- Request is purely informational ("what does Tradoor do?")

## Deterministic Dispatch Matrix

| Idea Category | Triage Action | Outcome |
|---|---|---|
| New product/platform (strategic) | Evaluate strategic fit → escalate to CEO if promising | CEO reviews with C-suite, decides build/research/archive |
| Feature enhancement (tactical) | Evaluate against current roadmap → route to product-manager | Feature added to backlog or declined with reason |
| Competitor-inspired feature | Analyze competitor gap → CTO for technical feasibility | Technical assessment + recommendation |
| Market expansion | Evaluate target market → CMO for market analysis | Market study + go/no-go recommendation |
| Strategic pivot | Full strategic review → CEO + C-suite debate | Pivot plan or archive with learning |
| Ecosystem contribution (OSS/tooling) | Evaluate community value → CTO | Contribution plan or decline |

## Workflow

### Phase 1: Intake & Classification

1. **Capture the idea** — restate in one sentence, identify the reference (if any)
2. **Classify** — new product, feature, competitor-inspired, market expansion, pivot, or ecosystem contribution
3. **Check existing coverage** — search SKILLS.json and brain for similar ideas (avoid duplicate work)
4. **Identify owner** — who proposed it, what's their stake

### Phase 2: Strategic Fit Evaluation

Score the idea on five dimensions (1–5 each):

| Dimension | Question | Evidence Required |
|---|---|---|
| **Company benefit** | Does this help 1ai's mission, revenue, or market position? | Concrete link to OKR or revenue line |
| **Ecosystem benefit** | Does this help the broader 1ai ecosystem (other projects, community, open source)? | Named ecosystem impact |
| **Feasibility** | Can we build it with current skills, agents, and infrastructure? | Technical assessment from CTO |
| **Cost** | Engineering hours, opportunity cost, ongoing maintenance | Estimate from CFO or product-manager |
| **Risk** | Reputational, financial, technical, or competitive risk | Risk assessment from relevant C-suite |

Total score: 25 max. Thresholds live in DECISION.md §2 (authority gates) and ROLES.md §2 (spend thresholds: L4 up to $1,000/transaction, >$1,000/transaction or >$3,000/month requires L5). Do not invent numeric thresholds.

### Phase 3: Decision

Score bands below are a skill-local 25-point heuristic (not defined in core rules) and never override DECISION.md §2 authority gates — any irreversible routing still requires L5 owner approval.

- **Score ≥15** → Escalate to CEO with full evaluation packet (idea, scores, evidence, recommendation)
- **Score 10–14** → Route to relevant C-suite for deeper analysis (CTO for technical, CMO for market, CFO for financial)
- **Score <10** → Archive with written rationale (logged per DECISION.md §4)

### Phase 4: Escalation Packet

If escalating, prepare:
1. **One-paragraph idea summary** — what, why, reference
2. **Strategic fit scores** — five dimensions with evidence
3. **Recommendation** — build now, research first, or archive
4. **Next step** — which C-suite should own the review

Send to `role-ceo` for review. CEO dispatches to C-suite for multi-department debate (see `role-ceo` workflow).

## Anti-Rationalization Table

| Rationalization | Reality | Required Discipline |
|---|---|---|
| "Owner said build it, just build it" | Owner ideas deserve evaluation, not blind obedience. Blind building wastes resources. | Always run triage; escalate with evidence, not obedience. |
| "Competitor has it, so we need it" | Competitors ship for their context, not ours. Copying without analysis is cargo-culting. | Analyze WHY they built it, then decide if the same logic applies to us. |
| "It's a small feature, just do it" | Small features compound into architecture debt. Every feature has maintenance cost. | Evaluate even small ideas — cost is more than build time. |
| "No time to research, just build" | Building without research is guessing. Research is cheaper than rework. | Time-box research (2–4 hours), then decide. |
| "If it fails, we'll just revert" | Reverting has cost: lost time, team morale, user trust. | Evaluate reversibility explicitly; log the cost of failure. |

## Verification Checklist

- [ ] Idea classified and restated in one sentence
- [ ] Existing coverage checked (SKILLS.json, brain, past decisions)
- [ ] Strategic fit scored on all five dimensions with evidence
- [ ] Decision made: escalate (≥15), research (10–14), or archive (<10)
- [ ] Escalation packet prepared with recommendation (if escalating)
- [ ] Decision logged in `logs/decisions/YYYY-MM-DD.md` per DECISION.md protocol
- [ ] If archived: rationale documented and communicated to owner

## Integration with 1ai-rules

- **DECISION.md**: All idea decisions are Type 1 (reversible — can revisit) or Type 2 (if committing significant resources). Log per §4 (DECISION LOG).
- **MULTI_AGENT.md**: When escalating, CEO uses multi-department debate (Advocate/Skeptic/Synthesizer per department).
- **SURPASS.md**: Research phase follows SURPASS protocol (Research → Analyze → Plan).
- **ROLES.md**: Owner is L5 (sovereign). Vilona is L4 (orchestrator). CEO is L4. This skill operates at L4.
- **INCIDENT.md**: If the idea is actually an incident response (e.g., "build a hotfix for production down"), route to INCIDENT protocol instead.

## Example: Tradoor Reference

**Input:** "Hey, I have an idea — what if we make this application like Tradoor as a reference?"

**Triage:**
1. **Classify:** Competitor-inspired feature (trading platform UI/UX)
2. **Strategic fit:**
   - Company benefit: 3/5 (aligns with trading/quant skills, but we're not a trading platform)
   - Ecosystem benefit: 2/5 (unclear — does this help other 1ai projects?)
   - Feasibility: 4/5 (we have trading skills, UI skills, backend skills)
   - Cost: 2/5 (significant — new platform, not a feature)
   - Risk: 3/5 (market risk, unclear demand)
   - **Total: 14/25** → Research first
3. **Decision:** Route to CTO for technical feasibility + CMO for market analysis
4. **Next step:** CTO evaluates if we can build a Tradoor-like trading platform with existing skills; CMO evaluates market demand and positioning

**Outcome:** Idea is logged, research is scoped, and CEO is notified for potential multi-department review if research confirms viability.
