Prompt file imported from shynlee04/project-alpha-master (.windsurf/workflows/write-spec/write-spec.md). Copyright stays with the author.

Now that we've initiated and planned the details for a new spec, we will now proceed with drafting the specification document, following these instructions:

Spec Writing

Name: write-spec
Author: shynlee04

Core Responsibilities

Analyze Requirements: Load and analyze requirements and visual assets thoroughly
Search for Reusable Code: Find reusable components and patterns in existing codebase
Create Specification: Write comprehensive specification document

Workflow

Step 1: Analyze Requirements and Context

Read and understand all inputs and THINK HARD:

# Read the requirements document
cat agent-os/specs/[current-spec]/planning/requirements.md

# Check for visual assets
ls -la agent-os/specs/[current-spec]/planning/visuals/ 2>/dev/null | grep -v "^total" | grep -v "^d"

Parse and analyze:

User's feature description and goals
Requirements gathered by spec-shaper
Visual mockups or screenshots (if present)
Any constraints or out-of-scope items mentioned

Step 2: Search for Reusable Code

Before creating specifications, search the codebase for existing patterns and components that can be reused.

Based on the feature requirements, identify relevant keywords and search for:

Similar features or functionality
Existing UI components that match your needs
Models, services, or controllers with related logic
API patterns that could be extended
Database structures that could be reused

Use appropriate search tools and commands for the project's technology stack to find:

Components that can be reused or extended
Patterns to follow from similar features
Naming conventions used in the codebase
Architecture patterns already established

Document your findings for use in the specification.

Step 3: Create Core Specification

Write the main specification to agent-os/specs/[current-spec]/spec.md.

DO NOT write actual code in the spec.md document. Just describe the requirements clearly and concisely.

Keep it short and include only essential information for each section.

Follow this structure exactly when creating the content of spec.md:

# Specification: [Feature Name]

## Goal

[1-2 sentences describing the core objective]

## User Stories

- As a [user type], I want to [action] so that [benefit]
- [repeat for up to 2 max additional user stories]

## Specific Requirements

**Specific requirement name**

- [Up to 8 CONCISE sub-bullet points to clarify specific sub-requirements, design or architectual decisions that go into this requirement, or the technical approach to take when implementing this requirement]

[repeat for up to a max of 10 specific requirements]

## Visual Design

[If mockups provided]

**`planning/visuals/[filename]`**

- [up to 8 CONCISE bullets describing specific UI elements found in this visual to address when building]

[repeat for each file in the `planning/visuals` folder]

## Existing Code to Leverage

**Code, component, or existing logic found**

- [up to 5 bullets that describe what this existing code does and how it should be re-used or replicated when building this spec]

[repeat for up to 5 existing code areas]

## Out of Scope

- [up to 10 concise descriptions of specific features that are out of scope and MUST NOT be built in this spec]

Important Constraints

Always search for reusable code before specifying new components
Reference visual assets when available
Do NOT write actual code in the spec
Keep each section short, with clear, direct, skimmable specifications
Do NOT deviate from the template above and do not add additional sections

Display confirmation and next step

Display the following message to the user:

The spec has been created at `agent-os/specs/[this-spec]/spec.md`.

Review it closely to ensure everything aligns with your vision and requirements.

Next step: Run the command, 2-create-tasks-list.md

Now that we've initiated and planned the details for a new spec, we will now proceed with drafting the specification document, following these instructions: # Spec Writing ## Core Responsibilities 1. **Analyze Requirements**: Load and analyze requirements and visual assets thoroughly 2. **Search for Reusable Code**: Find reusable components and patterns in existing codebase 3. **Create Specification**: Write comprehensive specification document ## Workflow ### Step 1: Analyze Requirements and Context Read and understand all inputs and THINK HARD: ```bash # Read the requirements document cat agent-os/specs/[current-spec]/planning/requirements.md # Check for visual assets ls -la agent-os/specs/[current-spec]/planning/visuals/ 2>/dev/null | grep -v "^total" | grep -v "^d" ``` Parse and analyze: - User's feature description and goals - Requirements gathered by spec-shaper - Visual mockups or screenshots (if present) - Any constraints or out-of-scope items mentioned ### Step 2: Search for Reusable Code Before creating specifications, search the codebase for existing patterns and components that can be reused. Based on the feature requirements, identify relevant keywords and search for: - Similar features or functionality - Existing UI components that match your needs - Models, services, or controllers with related logic - API patterns that could be extended - Database structures that could be reused Use appropriate search tools and commands for the project's technology stack to find: - Components that can be reused or extended - Patterns to follow from similar features - Naming conventions used in the codebase - Architecture patterns already established Document your findings for use in the specification. ### Step 3: Create Core Specification Write the main specification to `agent-os/specs/[current-spec]/spec.md`. DO NOT write actual code in the spec.md document. Just describe the requirements clearly and concisely. Keep it short and include only essential information for each section. Follow this structure exactly when creating the content of `spec.md`: ```markdown # Specification: [Feature Name] ## Goal [1-2 sentences describing the core objective] ## User Stories - As a [user type], I want to [action] so that [benefit] - [repeat for up to 2 max additional user stories] ## Specific Requirements **Specific requirement name** - [Up to 8 CONCISE sub-bullet points to clarify specific sub-requirements, design or architectual decisions that go into this requirement, or the technical approach to take when implementing this requirement] [repeat for up to a max of 10 specific requirements] ## Visual Design [If mockups provided] **`planning/visuals/[filename]`** - [up to 8 CONCISE bullets describing specific UI elements found in this visual to address when building] [repeat for each file in the `planning/visuals` folder] ## Existing Code to Leverage **Code, component, or existing logic found** - [up to 5 bullets that describe what this existing code does and how it should be re-used or replicated when building this spec] [repeat for up to 5 existing code areas] ## Out of Scope - [up to 10 concise descriptions of specific features that are out of scope and MUST NOT be built in this spec] ``` ## Important Constraints 1. **Always search for reusable code** before specifying new components 2. **Reference visual assets** when available 3. **Do NOT write actual code** in the spec 4. **Keep each section short**, with clear, direct, skimmable specifications 5. **Do NOT deviate from the template above** and do not add additional sections ## Display confirmation and next step Display the following message to the user: ``` The spec has been created at `agent-os/specs/[this-spec]/spec.md`. Review it closely to ensure everything aligns with your vision and requirements. Next step: Run the command, 2-create-tasks-list.md ```

{ "prompt": "Now that we've initiated and planned the details for a new spec, we will now proceed with drafting the specification document, following these instructions:\n\n# Spec Writing\n\n## Core Responsibilities\n\n1. **Analyze Requirements**: Load and analyze requirements and visual assets thoroughly\n2. **Search for Reusable Code**: Find reusable components and patterns in existing codebase\n3. **Create Specification**: Write comprehensive specification document\n\n## Workflow\n\n### Step 1: Analyze Requirements and Context\n\nRead and understand all inputs and THINK HARD:\n\n```bash\n# Read the requirements document\ncat agent-os/specs/[current-spec]/planning/requirements.md\n\n# Check for visual assets\nls -la agent-os/specs/[current-spec]/planning/visuals/ 2>/dev/null | grep -v \"^total\" | grep -v \"^d\"\n```\n\nParse and analyze:\n\n- User's feature description and goals\n- Requirements gathered by spec-shaper\n- Visual mockups or screenshots (if present)\n- Any constraints or out-of-scope items mentioned\n\n### Step 2: Search for Reusable Code\n\nBefore creating specifications, search the codebase for existing patterns and components that can be reused.\n\nBased on the feature requirements, identify relevant keywords and search for:\n\n- Similar features or functionality\n- Existing UI components that match your needs\n- Models, services, or controllers with related logic\n- API patterns that could be extended\n- Database structures that could be reused\n\nUse appropriate search tools and commands for the project's technology stack to find:\n\n- Components that can be reused or extended\n- Patterns to follow from similar features\n- Naming conventions used in the codebase\n- Architecture patterns already established\n\nDocument your findings for use in the specification.\n\n### Step 3: Create Core Specification\n\nWrite the main specification to `agent-os/specs/[current-spec]/spec.md`.\n\nDO NOT write actual code in the spec.md document. Just describe the requirements clearly and concisely.\n\nKeep it short and include only essential information for each section.\n\nFollow this structure exactly when creating the content of `spec.md`:\n\n```markdown\n# Specification: [Feature Name]\n\n## Goal\n\n[1-2 sentences describing the core objective]\n\n## User Stories\n\n- As a [user type], I want to [action] so that [benefit]\n- [repeat for up to 2 max additional user stories]\n\n## Specific Requirements\n\n**Specific requirement name**\n\n- [Up to 8 CONCISE sub-bullet points to clarify specific sub-requirements, design or architectual decisions that go into this requirement, or the technical approach to take when implementing this requirement]\n\n[repeat for up to a max of 10 specific requirements]\n\n## Visual Design\n\n[If mockups provided]\n\n**`planning/visuals/[filename]`**\n\n- [up to 8 CONCISE bullets describing specific UI elements found in this visual to address when building]\n\n[repeat for each file in the `planning/visuals` folder]\n\n## Existing Code to Leverage\n\n**Code, component, or existing logic found**\n\n- [up to 5 bullets that describe what this existing code does and how it should be re-used or replicated when building this spec]\n\n[repeat for up to 5 existing code areas]\n\n## Out of Scope\n\n- [up to 10 concise descriptions of specific features that are out of scope and MUST NOT be built in this spec]\n```\n\n## Important Constraints\n\n1. **Always search for reusable code** before specifying new components\n2. **Reference visual assets** when available\n3. **Do NOT write actual code** in the spec\n4. **Keep each section short**, with clear, direct, skimmable specifications\n5. **Do NOT deviate from the template above** and do not add additional sections\n\n## Display confirmation and next step\n\nDisplay the following message to the user:\n\n```\nThe spec has been created at `agent-os/specs/[this-spec]/spec.md`.\n\nReview it closely to ensure everything aligns with your vision and requirements.\n\nNext step: Run the command, 2-create-tasks-list.md\n```", "variables": [], "notes": "Now that we've initiated and planned the details for a new spec, we will now proceed with drafting the specification document, following these instructions:", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/shynlee04/project-alpha-master", "path": ".windsurf/workflows/write-spec/write-spec.md", "ref": "9c8401e68775164760fd2dd918e4c2d5ba7ed6e2", "url": "https://github.com/shynlee04/project-alpha-master/blob/9c8401e68775164760fd2dd918e4c2d5ba7ed6e2/.windsurf/workflows/write-spec/write-spec.md", "key": "shynlee04/project-alpha-master/.windsurf/workflows/write-spec/write-spec.md" } } }

write-spec

About

Spec Writing

Core Responsibilities

Workflow

Step 1: Analyze Requirements and Context

Step 2: Search for Reusable Code

Step 3: Create Core Specification

Important Constraints

Display confirmation and next step

Use it

Manifest

Reviews