Finalise — Car Fleet¶

The docs are done. The skill is created. Time to merge and set up for the next feature.

Update the living documents¶

Ask the agent:

Do the following in order:

1. Append an entry to CHANGELOG.md:
   YYYY-MM-DD — <feature-name>
   One sentence describing what was built.

2. If any implementation decision differed from specs/tech-design.md,
   update the relevant section to reflect the actual decision.

3. In specs/roadmap.md, mark the current feature status as "done".

Turn this into a skill¶

The same finalise steps will repeat for every feature. Ask the agent to package them:

/create-skill
Based on what we just did — updating CHANGELOG, syncing tech-design, marking the roadmap, merging, and replanning — create a skill at .cursor/skills/finalise-feature.md that automates this workflow for future features.

Reference skills¶

The ready branch of the workshop repo contains working skills you can study or use as a reference:

.cursor/skills/

Skill	What it does
`setup-al-vibe-rules.md`	Downloads AL vibe coding rules and writes AGENTS.md
`create-feature-spec.md`	Creates the feature spec branch and generates requirements, plan, and acceptance files
`generate-docs.md`	Generates the user guide section and runs the BC Code Intelligence docs review
`finalise-feature.md`	Updates CHANGELOG, syncs tech-design, marks roadmap, and commits

Merge to main¶

git checkout main
git merge spec/YYYY-MM-DD-fleet-register
git push

Clear context¶

Close this chat. The feature is done. The next feature gets a clean slate.

Replan →