---
name: agent-role-and-project-identity
description: "Project title, description, type, project code, and a project-appropriate agent role — sharpened rather than merely copied forward when existing content reads generic or thin. Use when a person asks to install or apply \"Agent Role & Project Identity\" (FTR-04) in a project, or when working in a project that has it installed."
---

# Agent Role & Project Identity (FTR-04, version 1.1)

> Generated from library record FTR-04 version 1.1, publish 20261102a. Review status: unreviewed. The complete specification is in references/spec.md and is the authority; this file is the operating procedure drawn from it.

## What this does

Project title, description, type, project code, and a project-appropriate agent role — sharpened rather than merely copied forward when existing content reads generic or thin

## When to use this skill

- A person asks to install, apply or update "Agent Role & Project Identity" (FTR-04) in a project.
- A project's agent instructions list agent-role-and-project-identity as installed and the task touches what it covers.
- No other feature is required first.
- Required by: FTR-08 (skill file-naming-and-versioning).

## Install procedure

Steps run in order. Assess comes first, every question in the Ask step is answered by the person before anything is written, and every write merges additively into the existing project files (read the file first, update an existing section in place, never overwrite).

### 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

The full Write payload is in references/write-payload.md. It is applied exactly as written, with the merge rule above.

### 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?

## Files in this skill

- references/spec.md: the complete specification, unabridged.
- references/write-payload.md: the Write step on its own.