Skills Implementation Spec Writer
Implementation Spec Writer
Use when you need a structured feature or engineering spec for a feature request, task, or tracker item.
Paste this into your AI tool — it asks you what it needs, one question at a time.
Ask me these questions one at a time. Wait for my answer before moving to the next. 1. What is the feature request, task summary, or tracker id? If you have an existing spec, paste that path or id. 2. What problem does this feature solve for the user or product? 3. What is in scope for this work? 4. What is explicitly out of scope? 5. What files, components, or existing behavior will this impact? 6. What acceptance criteria or verification steps should be included? Once I've answered all six, write a spec document with the following sections: - Summary - Motivation - Scope - Affected files - Implementation steps - Edge cases & risks - Acceptance criteria The spec should be concise, task-focused, and suitable for a tracker-based engineering workflow. Do not write code or change file contents.
Example output
# Implement user settings persistence - **Tracker:** T014 - **Date:** 2026-05-31 ## Summary Add persistent user settings so the app restores the last selected workspace, theme, and provider after restart. ## Motivation Users currently lose their workspace and provider choice after closing the app. This makes the product feel unstable and slows repeat use. ## Scope In scope: save and restore workspace path, selected theme, and provider config. Out of scope: onboarding UI redesign and new provider integrations. ## Affected files - `src-tauri/src/commands/config.rs` — read/write persisted settings - `src/store/sessionStore.ts` — restore session state on app load - `src/components/Onboarding/index.tsx` — skip workspace step for returning users ## Implementation steps 1. **Define persistence keys** (`config.rs`) and ensure they serialize to the app config store. 2. **Load settings on startup** (`sessionStore.ts`) before `sendMessage` or session creation. 3. **Write settings updates** when workspace, theme, or provider changes. 4. **Verify restore flow** by restarting the app and confirming the previous settings reappear. ## Edge cases & risks - Handle invalid or deleted workspace paths gracefully. - Do not persist sensitive API keys in plain text. - If app config migration is needed, preserve existing user data. ## Acceptance criteria - [ ] Workspace path, theme, and provider are restored after restart - [ ] No runtime errors occur during settings load - [ ] User can still change settings and have them persist