Application Functionality Requirements Planning Skill

Use this skill when writing, reviewing, or improving application functionality documentation, product requirements, feature checklists, scope constraints, roadmaps, or security/authorization requirements.

The goal is to produce requirements that are clear, testable, implementation-aware, and safe to build.

Core Principle

Application functionality documentation must describe:

1. What the system does.
2. Who can use each capability.
3. What is intentionally out of scope.
4. What security and permission rules apply.
5. How well the system must perform.
6. What data, integrations, telemetry, and migration impacts exist.
7. What counts as done.

Do not write only UI behavior. For every important capability, also describe backend rules, data ownership, constraints, and acceptance criteria.