Prompt file imported from geokrety/geokrety-stats (.github/prompts/2.create-specs.prompt.md). Copyright stays with the author.

ABSOLUTE GOAL

Name: 2.create-specs
Author: geokrety

create a complete specification file in #file:../../tmp/yyyymmdd-short-description/specification.md (where yyyymmdd-short-description is a unique identifier for this specification).

Instructions

you MUST create a "specs file" #file:../../tmp/yyyymmdd-short-description/specification.md where yyyymmdd-short-description is a unique identifier for this prompt.

you MUST use agent "specification" to generate the specification file based on the user input and the context provided by the codebase and database.
you MUST ensure that the specification file is comprehensive, clear, and well-structured, covering all relevant aspects of the feature or functionality being specified.
you MUST use the template provided below to structure the specification file, and you MUST fill in each section with detailed and accurate information based on the requirements and design of the feature.
once you have created the specification, you MUST use the "critical-loop" skill with agents "specification" -> "technical-writer" -> "requirements-analyst" -> "critical-thinking" to review the generated specification file and ensure that it meets the requirements, is of high quality, and is ready for implementation.
lastly you must use the SKILL last-user-input #file:../skills/last-user-input/SKILL.md to ask the user if they have any last requests or changes before you finalize the specification and mark the task as complete. This is crucial to ensure that you have met the user's expectations and requirements and that you have not missed any important details. Always confirm with the user before finalizing your specification to avoid any misalignment or unmet requirements.

specification file template

# Specification for [Feature/Functionality Name]

## Overview
- Brief description of the feature or functionality being specified.

## Requirements
- List of functional and non-functional requirements that the feature must meet.

## Design
- Detailed design of the feature, including architecture, components, and interactions.

## Implementation Details
- Specific implementation details, such as algorithms, data structures, and technologies to be used.

## Testing
- Description of the testing strategy, including types of tests to be performed and tools to be used

## Acceptance Criteria
- Clear and measurable criteria that must be met for the feature to be considered complete and ready for deployment.

## Diagrams and Examples
- Any relevant diagrams, examples, or references to support the specification and enhance understanding.

## Deliverables
- List of deliverables that will be produced as part of the implementation of this feature.

## Implementation checklist

# ABSOLUTE GOAL - create a complete specification file in #file:../../tmp/yyyymmdd-short-description/specification.md (where `yyyymmdd-short-description` is a unique identifier for this specification). ## Instructions - you MUST create a "specs file" #file:../../tmp/yyyymmdd-short-description/specification.md where `yyyymmdd-short-description` is a unique identifier for this prompt.  - you MUST use agent "specification" to generate the specification file based on the user input and the context provided by the codebase and database. - you MUST ensure that the specification file is comprehensive, clear, and well-structured, covering all relevant aspects of the feature or functionality being specified. - you MUST use the template provided below to structure the specification file, and you MUST fill in each section with detailed and accurate information based on the requirements and design of the feature. - once you have created the specification, you MUST use the "critical-loop" skill with agents "specification" -> "technical-writer" -> "requirements-analyst" -> "critical-thinking" to review the generated specification file and ensure that it meets the requirements, is of high quality, and is ready for implementation. - lastly you must use the SKILL `last-user-input` #file:../skills/last-user-input/SKILL.md to ask the user if they have any last requests or changes before you finalize the specification and mark the task as complete. This is crucial to ensure that you have met the user's expectations and requirements and that you have not missed any important details. Always confirm with the user before finalizing your specification to avoid any misalignment or unmet requirements. # specification file template ```md # Specification for [Feature/Functionality Name] ## Overview - Brief description of the feature or functionality being specified. ## Requirements - List of functional and non-functional requirements that the feature must meet. ## Design - Detailed design of the feature, including architecture, components, and interactions. ## Implementation Details - Specific implementation details, such as algorithms, data structures, and technologies to be used. ## Testing - Description of the testing strategy, including types of tests to be performed and tools to be used ## Acceptance Criteria - Clear and measurable criteria that must be met for the feature to be considered complete and ready for deployment. ## Diagrams and Examples - Any relevant diagrams, examples, or references to support the specification and enhance understanding. ## Deliverables - List of deliverables that will be produced as part of the implementation of this feature. ## Implementation checklist ```

{ "prompt": "\n\n\n# ABSOLUTE GOAL\n\n- create a complete specification file in #file:../../tmp/yyyymmdd-short-description/specification.md (where `yyyymmdd-short-description` is a unique identifier for this specification).\n\n## Instructions\n\n- you MUST create a \"specs file\" #file:../../tmp/yyyymmdd-short-description/specification.md where `yyyymmdd-short-description` is a unique identifier for this prompt.\n\n- you MUST use agent \"specification\" to generate the specification file based on the user input and the context provided by the codebase and database.\n- you MUST ensure that the specification file is comprehensive, clear, and well-structured, covering all relevant aspects of the feature or functionality being specified.\n- you MUST use the template provided below to structure the specification file, and you MUST fill in each section with detailed and accurate information based on the requirements and design of the feature.\n- once you have created the specification, you MUST use the \"critical-loop\" skill with agents \"specification\" -> \"technical-writer\" -> \"requirements-analyst\" -> \"critical-thinking\" to review the generated specification file and ensure that it meets the requirements, is of high quality, and is ready for implementation.\n- lastly you must use the SKILL `last-user-input` #file:../skills/last-user-input/SKILL.md to ask the user if they have any last requests or changes before you finalize the specification and mark the task as complete. This is crucial to ensure that you have met the user's expectations and requirements and that you have not missed any important details. Always confirm with the user before finalizing your specification to avoid any misalignment or unmet requirements.\n\n# specification file template\n\n```md\n# Specification for [Feature/Functionality Name]\n\n## Overview\n- Brief description of the feature or functionality being specified.\n\n## Requirements\n- List of functional and non-functional requirements that the feature must meet.\n\n## Design\n- Detailed design of the feature, including architecture, components, and interactions.\n\n## Implementation Details\n- Specific implementation details, such as algorithms, data structures, and technologies to be used.\n\n## Testing\n- Description of the testing strategy, including types of tests to be performed and tools to be used\n\n## Acceptance Criteria\n- Clear and measurable criteria that must be met for the feature to be considered complete and ready for deployment.\n\n## Diagrams and Examples\n- Any relevant diagrams, examples, or references to support the specification and enhance understanding.\n\n## Deliverables\n- List of deliverables that will be produced as part of the implementation of this feature.\n\n## Implementation checklist\n\n```", "variables": [], "notes": "Generate a new specification file in the docs. Tools: vscode/askQuestions, execute/runInTerminal, read/problems, read/readFile, agent, edit/createFile, edit/editFiles, search/changes, search/codebase, search/fileSearch, search/listDirectory, search/textSearch.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/geokrety/geokrety-stats", "path": ".github/prompts/2.create-specs.prompt.md", "ref": "f90bf143462e2d740c08b13bc2db64f99a7c8faf", "url": "https://github.com/geokrety/geokrety-stats/blob/f90bf143462e2d740c08b13bc2db64f99a7c8faf/.github/prompts/2.create-specs.prompt.md", "key": "geokrety/geokrety-stats/.github/prompts/2.create-specs.prompt.md" } } }

2.create-specs

About

ABSOLUTE GOAL

Instructions

specification file template

Use it

Manifest

Reviews