/**
 * Default content for spec template
 *
 * This template is used when creating new feature specifications.
 * It can be customized by placing a spec-template.md file in the
 * project's .specify/templates directory.
 */
export declare const SPEC_TEMPLATE_CONTENT = "# Feature Specification: [FEATURE NAME]\n\n**Feature Branch**: `[###-feature-name]`\n**Created**: [DATE]\n**Status**: Draft\n**Input**: User description: \"$ARGUMENTS\"\n\n## User Scenarios & Testing *(mandatory)*\n\n<!--\n  IMPORTANT: User stories should be PRIORITIZED as user journeys ordered by importance.\n  Each user story/journey must be INDEPENDENTLY TESTABLE - meaning if you implement just ONE of them,\n  you should still have a viable MVP (Minimum Viable Product) that delivers value.\n\n  Assign priorities (P1, P2, P3, etc.) to each story, where P1 is the most critical.\n  Think of each story as a standalone slice of functionality that can be:\n  - Developed independently\n  - Tested independently\n  - Deployed independently\n  - Demonstrated to users independently\n-->\n\n### User Story 1 - [Brief Title] (Priority: P1)\n\n[Describe this user journey in plain language]\n\n**Why this priority**: [Explain the value and why it has this priority level]\n\n**Independent Test**: [Describe how this can be tested independently - e.g., \"Can be fully tested by [specific action] and delivers [specific value]\"]\n\n**Acceptance Scenarios**:\n\n1. **Given** [initial state], **When** [action], **Then** [expected outcome]\n2. **Given** [initial state], **When** [action], **Then** [expected outcome]\n\n---\n\n### User Story 2 - [Brief Title] (Priority: P2)\n\n[Describe this user journey in plain language]\n\n**Why this priority**: [Explain the value and why it has this priority level]\n\n**Independent Test**: [Describe how this can be tested independently]\n\n**Acceptance Scenarios**:\n\n1. **Given** [initial state], **When** [action], **Then** [expected outcome]\n\n---\n\n### User Story 3 - [Brief Title] (Priority: P3)\n\n[Describe this user journey in plain language]\n\n**Why this priority**: [Explain the value and why it has this priority level]\n\n**Independent Test**: [Describe how this can be tested independently]\n\n**Acceptance Scenarios**:\n\n1. **Given** [initial state], **When** [action], **Then** [expected outcome]\n\n---\n\n[Add more user stories as needed, each with an assigned priority]\n\n### Edge Cases\n\n<!--\n  ACTION REQUIRED: The content in this section represents placeholders.\n  Fill them out with the right edge cases.\n-->\n\n- What happens when [boundary condition]?\n- How does system handle [error scenario]?\n\n## Requirements *(mandatory)*\n\n<!--\n  ACTION REQUIRED: The content in this section represents placeholders.\n  Fill them out with the right functional requirements.\n-->\n\n### Functional Requirements\n\n- **FR-001**: System MUST [specific capability, e.g., \"allow users to create accounts\"]\n- **FR-002**: System MUST [specific capability, e.g., \"validate email addresses\"]\n- **FR-003**: Users MUST be able to [key interaction, e.g., \"reset their password\"]\n- **FR-004**: System MUST [data requirement, e.g., \"persist user preferences\"]\n- **FR-005**: System MUST [behavior, e.g., \"log all security events\"]\n\n*Example of marking unclear requirements:*\n\n- **FR-006**: System MUST authenticate users via [NEEDS CLARIFICATION: auth method not specified - email/password, SSO, OAuth?]\n- **FR-007**: System MUST retain user data for [NEEDS CLARIFICATION: retention period not specified]\n\n### Key Entities *(include if feature involves data)*\n\n- **[Entity 1]**: [What it represents, key attributes without implementation]\n- **[Entity 2]**: [What it represents, relationships to other entities]\n\n## Success Criteria *(mandatory)*\n\n<!--\n  ACTION REQUIRED: Define measurable success criteria.\n  These must be technology-agnostic and measurable.\n-->\n\n### Measurable Outcomes\n\n- **SC-001**: [Measurable metric, e.g., \"Users can complete account creation in under 2 minutes\"]\n- **SC-002**: [Measurable metric, e.g., \"System handles 1000 concurrent users without degradation\"]\n- **SC-003**: [User satisfaction metric, e.g., \"90% of users successfully complete primary task on first attempt\"]\n- **SC-004**: [Business metric, e.g., \"Reduce support tickets related to [X] by 50%\"]\n";
//# sourceMappingURL=spec.d.ts.map