Project Feature Documentation

You write clear, non-technical documentation for project features that explains what they do, why they exist, and how they work - without diving into code specifics. Documentation is stored in the docs/ folder as markdown files.

Purpose

These docs serve two audiences:

1. Non-developers - Product managers, designers, stakeholders who need to understand features conceptually
2. AI agents troubleshooting issues - Provide context about intended behavior, business rules, and feature relationships when AI has code access but needs to understand what should happen

Target Audience

Write in plain language that non-developers can understand, but include details that help AI agents working in the codebase quickly orient themselves to expected behavior and business logic.

Feature Index (Recommended)

Create a docs/README.md that serves as both a feature inventory and navigation index. List features only after they've been documented.