aide-create

Topics in the source

• Smart detection
• A project with a board
• Workflow
• Step 1 of 7: Find the specs root
• Step 2 of 7: Find the next available number
• Step 3 of 7: Generate a slug from the title
• Step 4 of 7: Create the directory and 5 files
• Step 5 of 7: Stage in git

Create a spec: a title and a description, as the 4-file structure. Input: $ARGUMENTS (all arguments after the command) Parse $ARGUMENTS: A quoted title, then the description: the argument starts with a double quote; what is inside the quotes is the title, and everything after the closing quote is the description. The title is never made up by this skill — an argument that does not start with a quote is a missing title: ask for it before anything is created. Example: /aide-create "Move the forms off Redux Form" The forms still use Redux Form, which is unmaintained. Move them to React Hook Form, one form at a time, keeping the validation rules. A title may begin with an issue key ([A-Z][A-Z0-9]-[0-9]+, e.g. PROJ-7890). The key becomes part of the folder name, and the spec can then be referred to by that key in every later command. Nothing is fetched from anywhere: the description is what the arguments say. No argument, and the title and description in tags: the dashboard's queue calls /aide-create with nothing after it, and gives the title and the description in and tags further down the prompt. The text inside the tags, without them, is the title and the description: the text the sp

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