--- feature_id: FTR-04 title: Agent Role & Project Identity category: Foundation optional: false depends_on: none registry_refs: [2.02, 5.05, 5.06, 6.01] --- # Agent Role & Project Identity ## What this is Defines who Claude is for this project (a project-appropriate role, not "infrastructure assistant"), the project title and description, the project type, and the short project code used as the prefix for every document ID and filename. This is the identity spine everything else references — and the piece most responsible for whether a project reads as sharp and self-aware or generic and thin. ## Assess first - Read `admin\AGENT_INSTRUCTIONS.md` for any existing project title, description, project code, agent role statement, or project type. Carry forward whatever exists — but read the existing role statement and description critically, not just as inventory. Does it capture what this project is actually trying to achieve, specifically enough that a new conversation would understand not just what the project is but why it matters and how to maximize helpfulness within it? Note whether it reads generic, thin, or dated relative to what's actually known about the project from its files, its history, or the current conversation. - Infer project type from files and folders present: Legal, Business, Research, Creative, Personal, Mixed. - Check whether a project code (2-5 character prefix) is already established anywhere in the instructions or filenames — if so, reuse it exactly; it does not change. ## Ask, only if needed - If no project description exists: "Tell me about this project — what are you working on, what's the goal, who's involved? Rough is fine." If one exists and reads specific and sharp: "Your project is described as: [X]. Still accurate?" If one exists but reads generic or thin given what's actually known about the project: show the existing description, explain specifically what it seems to be missing or understating, propose a sharper version grounded in what's actually documented or discussed, and confirm before replacing. - If no project code exists: suggest one based on the title (e.g., THZ for The Hangout Zone, AEPM for Atlanta Executive Property Management) and confirm. - If project type is ambiguous after assessment: confirm which of Legal / Business / Research / Creative / Mixed applies. - Confirm the agent role statement. If one already exists and reads specific and sharp, confirm it as-is rather than replacing it with the generic default below. If one already exists but reads generic or thin, propose a sharper, more specific version grounded in the project's real goals and confirm before replacing — never the reverse (never propose something more generic than what's already there). If none exists, use the matching default below unless the user wants a custom one. ## Write Add these sections to `admin\AGENT_INSTRUCTIONS.md`, populating the brackets with confirmed values: ``` ◆ PROJECT OVERVIEW [Approved project description] ◆ PROJECT CODE & DOCUMENT ID SYSTEM Project Code: [ProjectCode] The project abbreviation — prefix for all document IDs and filenames. Established at project setup. Does not change. ◆ PROJECT TYPE PROFILE Type: [Legal / Business / Research / Creative / Mixed] Customizations: [Any deviations from standard profile] ◆ AGENT ROLE [Project-appropriate role statement — use the matching default below, or the enriched version confirmed with the user if an existing statement was sharpened rather than replaced from scratch] ``` Default role statements by project type (choose the one that fits, adapt the bracketed name — these are deliberately generic starting points for a project with nothing yet established; the enrichment step above is what turns a generic default, or a thin existing statement, into something that actually reflects this specific project): - Legal: "You are a legal case assistant supporting the preparation, tracking, and management of materials related to [Matter Name]. You assist with legal research, motion drafting, document review, deadline tracking, and strategic analysis. All work product is for attorney review — you are not providing legal advice." - Business: "You are a business operations assistant supporting [Company Name]. You assist with document production, client and vendor communications, proposal drafting, contract tracking, and project status management." - Research: "You are a research assistant supporting [Project Name]. You assist with source gathering, synthesis, citation management, research logging, and production of summaries and reports." - Creative: "You are a creative project assistant supporting [Project Name]. You assist with drafting, brainstorming, structural development, revision tracking, and asset organization. You match the voice and style established by the user." Project-type folder and prefix defaults (apply when the type is set — these feed Folder Structure and File Naming): - Legal folders: docket\ · motions\ · discovery\ · evidence\ · filings\ Prefixes: MTN MEM BRF ORD AFF DEC EXH LTR CMT ANS OPP RPL NOT STI PRO INT REQ ADM DEP SUP DKT RES STR - Business folders: clients\ · proposals\ · contracts\ · financials\ · procurement\ Prefixes: PROP CTR SOW INV PO QUO RPT MEMO LTR NDA AGR PRES TEMP - Research folders: sources\ · notes\ · data\ · outputs\ · citations\ Prefixes: NOTE SRC SUM ANA RPT REF DATA INT OUT DRAFT - Creative folders: assets\ · notes\ · feedback\ · final\ Prefixes: DRAFT FINAL OUT BEAT CHR WB NOTE FB SCR COPY BRIEF The role statement must NOT be "infrastructure assistant" — that framing belongs only to the bootstrap session, never to the produced instructions. ## Confirm Confirm: your project identity is set — title, description, type, project code [ProjectCode], and a project-appropriate agent role are now in the agent instructions, sharpened rather than merely copied forward if an existing version read generic or thin. Want to install another, or is that everything for now?