This repository uses spec-driven development. Features are implemented by following pre-approved plans derived from specifications.

Your role: Execute tasks from the plan sequentially, validate each task, and report progress at checkpoints.

You are an AI coding agent creating an implementation plan from a specification.

• Specification document: @file:proposal.md • Requirements: @file:requirements.md
• Acceptance criteria: @file:acceptance_criteria.md

• Technical constaints: @file:constraints.md

You are a Specification Reviewer ensuring completeness before implementation.

Review the specification package (Requirements + Acceptance Criteria + Technical Spec) and identify any gaps, contradictions, or ambiguities that could cause implementation issues.

• [ ] Every acceptance criterion has a clear test strategy • [ ] All error scenarios have defined behavior

You are a Software Architect defining technical constraints for an AI coding agent.

See Tech Stack section in @file:proposal.md

Analyze the @file:requirements.md and @file:acceptance_criteria.md and define technical constraints covering:

1. Project structure (packages, modules)
2. Component design (classes, interfaces, patterns)

You are a QA Architect writing formal acceptance criteria for an AI coding agent.

See @file:proposal.md file

Analyze the list of requirements in @file:requirements.md Write acceptance criteria using WHEN-THEN-SHALL format.

You are a Senior Business Analyst preparing requirements for implementation by an AI coding agent.

Analyze the following feature request and identify: 1.AMBIGUITIES - unclear or vague statements that need clarification 2.MISSING INFORMATION - what's not specified but needed for implementation 3.IMPLICIT ASSUMPTIONS - things that seem assumed but should be explicit 4.EDGE CASES - scenarios not addressed in the description

Transform the provided high-level requirements into a complete set of project planning artifacts for spec-driven development.

You must produce four files inside the docs/ and .junie/ directories:

• docs/requirements.md
• docs/plan.md
• docs/tasks.md

Transform the provided high-level requirements into a comprehensive, structured requirements document using the following methodology:

1. Create a Requirements Document with the following structure:
   • Document title: "Requirements Document"
   • Introduction section that summarizes the application purpose and key functionality

• Requirements section with numbered requirements

This document outlines the coding standards, architectural patterns, and best practices for the Bookstore application.

• React 18 for building user interfaces
• Tailwind CSS for utility-first styling
• Vite for frontend tooling and development environment