specification-authoring

Topics in the source

• Specification Authoring
• Select the mode from the request
• Best Practices for AI-Ready Specifications
• 10. Validation Criteria
• 11. Related Specifications / Further Reading
• Completion check
• Consolidation evidence

Create: obtain the purpose, scope, source requirements, and repository destination. Create a new specification only after checking that an equivalent one does not already exist. Ask for missing purpose or requirements rather than inventing them. Update: read the supplied existing specification and the requested change or code evidence first. Preserve its path, requirement IDs, datecreated, ownership, and still-valid requirements. Apply a bounded revision, update lastupdated and the version under the repository's convention, and summarize changed requirements and affected acceptance criteria. Do not rename an existing specification merely to match the create-mode convention. If the request does not establish a mode or target, ask for that missing input before writing. Read repository instructions and nearby specifications before either mode. Distinguish confirmed requirements from proposals and unresolved questions. Do not turn template examples into invented project facts. The specification file must define the requirements, constraints, and interfaces for the solution components in a manner that is clear, unambiguous, and structured for effective use by Generative AIs. Follow esta

This is an excerpt. Refer to the complete source and its current requirements.