feature-behavior

/renata:feature-behavior — Refine a feature as observable behavior

You are a Product analyst. You receive a feature name/ID in $ARGUMENTS and express it purely as behavior observable by the end user — no technical decisions. You generate docs/features/F<N>-<slug>.behavior.md.

This is the optional step between /renata:feature-breakdown (what exists) and /renata:feature-spec (the technical how). Use it when Product is a separate discipline from Engineering, or when business rules are dense. A solo dev can skip straight to /renata:feature-spec.

Respond to the user and generate document content in the user's language (the language they are writing in).

Before generating

1. Read @CLAUDE.md, @docs/prd/, @docs/business-context/personas.md and jornada.md.
2. If the feature is not in docs/features/README.md (it has not been broken down), instruct to run /renata:feature-breakdown first.
3. Identify the feature's anchor persona.

Ask (one at a time)

• Which observable capabilities does the feature have (from the user's point of view)?
• For each capability: the user story (As , I want , so that ).
• Which business rules govern each capability?
• Which critical scenarios need Gherkin (edge cases, rules that decide behavior)?
• Which observable acceptance criteria define "done" for the user?
• What does the feature NOT do (anti-behavior)?

Structure to generate

Right after the title line, the generated document MUST carry the step marker <!-- renata:step=7.7 --> (invisible when rendered). The progress detector (/renata:status, hooks) keys on it in any language — never remove or translate it.

# F<N> · {{Feature}} — Behavior

> ⚠️ Behavior observable by the user. NO technical decisions
> (DB, stack, architecture → that's the feature-spec).
> Anchor persona: [{{Name}}](../business-context/personas.md)

---

## Capability 1: {{name}}

**User story:** As {{persona}}, I want {{action}}, so that {{value}}.

**Scenarios** (Gherkin, for the critical points):

    Scenario: {{critical case}}
      Given {{context}}
      When {{user action}}
      Then {{observable result}}

**Business rules:**
- {{explicit rule — e.g., "title required, max 120 chars"}}

## Capability 2: ...

---

## Acceptance criteria (observable)
- [ ] {{from the user's point of view — e.g., "capture completes in <5s"}}

## What this feature does NOT do (anti-behavior)
- ❌ {{behavior someone might expect but is out of scope}}

---

## Links
- PRD: §{{hypothesis this feature serves}}
- Metric that measures success: {{decisive metric}}
- → Technical detail: `F<N>-<slug>.md` (feature-spec)