Role and Responsibilities

What This File Is For

This is an operational description of your work — what your weeks actually look like, what you're accountable for, what you produce. Agents use this to understand the rhythm and shape of your job so they can help with the right things at the right times. It's not a job description. It's a field guide to how you actually spend your days.

Interview Protocol

Hand this entire file to your AI build partner and say "let's do this one." Your build partner should read the instructions below and run the interview.

Instructions for the build partner: You're helping the user create their role and responsibilities file. This should capture the operational reality of their work, not the idealized version. Ask the following questions one at a time. Use what you already know from the identity file (if completed) to skip redundant questions and ask better follow-ups.

Questions to ask:

  1. Walk me through a typical week. What are the recurring things that happen every week without fail?
  2. What are you directly accountable for — what are the things where if they don't happen, it's on you?
  3. What decisions do you make regularly? Not the big strategic ones — the routine ones that come up every week.
  4. What do you produce? Reports, analyses, plans, code, presentations — what are the actual outputs of your work?
  5. Who do you report to? Who reports to you, if anyone?
  6. Are there monthly or quarterly rhythms that shape your work — planning cycles, reviews, board meetings, anything like that?

When you have enough: After 4-6 questions. This file is medium length. Capture the operational reality, not every edge case.

After drafting: Present the draft and ask the user to identify anything that doesn't sound right. Pay particular attention to whether the cadences and rhythms are accurate — people often forget recurring obligations until they see them missing.

Output Structure

# Role and Responsibilities

## Core Responsibilities

[What you're accountable for — the things that are unambiguously on you.]

## Weekly Cadence

[Recurring meetings, check-ins, deadlines, rituals. The skeleton of a typical week.]

## Monthly / Quarterly Rhythms

[Planning cycles, reviews, reporting periods, seasonal patterns. The bigger loops.]

## Key Decisions

[The decisions you make regularly — what comes across your desk that requires your judgment.]

## What I Produce

[Your outputs — deliverables, artifacts, reports, plans, code, whatever you create as part of your work.]

## Reporting Structure

[Who you report to, who reports to you. Keep it simple — names and roles.]