Features
The Functional Specification is the stage where you turn the requirements and product goals defined in the PRD into concrete, implementable features. If the PRD focuses on 'what to build and why', the Functional Specification is the document that designs 'how it works'.
The feature data defined here serves as the basis for every downstream planning artifact, including the User Flow. The Functional Specification provides two views: Tree View for managing the overall structure, and Directory View for managing detailed policies and descriptions.
1. Understanding the Structure
The Functional Specification is organized in a three-level hierarchy: Requirement → Feature → Specification.
Member management
Sign up
Email/password-based sign up
Social login (Kakao, Naver, Google, etc.)
Set nickname
Agree to Terms of Service and Privacy Policy
Login/Logout
Auto-login / logout handling
Find and reset password
Reservation management
Create reservation
Select meeting room and time slot
Add attendees and set capacity limits
Send reservation confirmation notifications
Requirement
Represents a top-level goal of the Project or a core need of the user.
Description: A unit that captures the major branches of the plan. (e.g. "Member management", "Payment and pricing")
Acceptance Criteria: The conditions or policies the Requirement must ultimately satisfy, defined as a checklist.
e.g. "Sign-up via email is possible", "Menus appear differently depending on the role's permissions"
Feature
A logical functional unit that concretely fulfills a Requirement.
Description: Defines the specific Features needed to achieve a Requirement. (e.g. "Sign up", "Document sharing", "Payment management")
User role: Specifies who performs each Feature. You can pull in the roles set in the PRD and match them here.
e.g. "Planner", "Admin", "Guest"
Specification
The lowest level, defining the actual detailed behavior or business policy that takes place within each Feature.
Description: A detailed spec that becomes the direct reference for development and design. (e.g. "Email signup validation", "Password reset logic", "Login session expiration policy")
Managing item attributes
At every level (Requirement, Feature, Specification), you can set the following attributes to systematically manage the priority and progress of your plan.
Priority: Sets the priority of the item. (Low / Medium / High)
Status: Sets the planning or development progress. (Not started / In progress / Done / Stopped)
You can flexibly use this as a planning progress tracker or a development status board, depending on your intent.
2. Switching Views
Move freely between the Tree View and the Directory View to fit the type of work you're doing, and elevate the quality of your plan.
Use the top tab toggle: Each time you click the [Functional Specification] tab at the top of the screen, the view alternates between Tree View and Directory View.
Use the left-side buttons: Click the icon buttons on the left edge of the screen to jump directly to the view you want.
Last updated