Identity Company

If it doesn't exist:

• Create the ~/.harness/identity/ directory if needed (use Bash: mkdir -p ~/.harness/identity/)
• Proceed directly to the interview

Interview Flow

Ask ONE question at a time. Wait for the user's response before asking the next question. Adapt to context — a solo freelancer needs different questions than a startup founder or enterprise employee.

Core Questions (always ask)

Question 1: What the Company Does "What does your company do? In a sentence or two, what's the core product or service, and who does it serve?"

If the user is a solo freelancer or independent, adapt: "What do you do professionally? What kind of work or clients do you focus on?"

Question 2: Industry & Market "What industry are you in, and who are your typical customers or users? Any specific market segment or niche?"

Question 3: Size & Stage "How big is the company? Think about team size, growth stage (bootstrapped, funded, scaling), and whether you operate locally or globally."

For solos/freelancers: "Are you working solo, or do you have a team? What stage is your business at?"

Question 4: Team Structure "How is your team organized? Who are the key roles, and who makes the important decisions?"

For solos: "Do you work with collaborators, contractors, or clients directly? Who are the key people in your work?"

Optional Depth Questions

Question 5: Domain Terminology "Are there industry-specific terms, acronyms, or jargon that agents should know? Terms that are commonly misused or have specific meaning in your context?"

Question 6: Competitive Context "Any important context about your competitive landscape or market position that would help agents make better product decisions?"

Adapting Questions

• For solo freelancers: skip or reframe team/company questions — focus on their work context and clients
• For startup founders: emphasize stage, market, and what makes them different
• For enterprise employees: focus on their division/team, not the whole corporation
• Brief answers are fine — generate with what you have
• Never ask a wall of questions — one at a time

Output Format

After completing the interview, generate the company identity file:

# Company Identity

Generated: {today's date in YYYY-MM-DD format}

## Mission & Product

{Synthesize from Question 1. What the company does, who it serves, what problem it solves. 2-4 sentences.}

## Industry & Market

{Synthesize from Question 2. Industry, market segment, customer profile. Include competitive context if discussed.}

## Size & Stage

{Synthesize from Question 3. Team size, growth stage, geographic scope. Be specific.}

## Team Structure

{Synthesize from Question 4. Key roles, decision-making structure. For solos, capture their working relationships.}

## Domain Terminology

{Synthesize from Question 5, or note "No specific domain terminology documented" if not discussed.}

| Term | Definition |
|------|-----------|
| {term} | {definition} |

Quality guidelines:

• Target 60-100 lines total
• Use the user's own language and framing
• Be specific — "B2B SaaS for construction project management" beats "a technology company"
• Adapt the structure for solos/freelancers — don't force corporate framing on individuals
• No YAML frontmatter on the identity file itself

Save the File

Write the generated content to ~/.harness/identity/company.md using the Write tool.

Report completion: "Company identity saved to ~/.harness/identity/company.md. Your agents now understand your business context."

Guardrails

• ONE question at a time — never a wall of questions
• Keep the interview under 5 minutes (3-6 questions total)
• Adapt language to the company type — don't use startup jargon for enterprises or vice versa
• If the user is a solo/freelancer, reframe company questions to personal context
• Capture what matters, skip what doesn't
• If the user wants to stop early, generate with what you have