aide-archive

Topics in the source

• A project with a board
• Workflow
• Step 1 of 5: Move the spec to the archive
• Step 2 of 5: Close the loop
• Step 3 of 5: Commit
• Step 4 of 5: Confirm
• Step 5 of 5: Merge into main

Archive a finished spec: settle any merge conflict on its branch, stamp it, move it to archive/, and merge what should outlive it into the project's living documentation. Input: $ARGUMENTS (a spec number, a full folder ID, or an issue key its title began with) Working interactively, hand the step to the board first: Exit 3, or no such command: go on with Step 1. Any other exit: its output is your last words; do nothing else. -- The steps below are this skill's own, inside the queue's archive step. Mark each one in the log, so a reader can follow the run: when it starts, write one line --- Step N of X: — started, and when it ends, one line --- Step N of X: — done. A step that ends the run early says — stopped: in place of — done, and one that does not apply to this run — skipped: . Step 5, the merge into the default branch, is Aide's, after this session: Aide writes its marks, and the archive is finished only when it is done. First write --- Step 1 of 5: Move the spec to the archive — started, and when this step ends, --- Step 1 of 5: Move the spec to the archive — done. A script does everything mechanical: resolving the argument to a folder, checking whether a merge is open, readin

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