add-item
Use when the user says "file an issue", "log this", "track this", "add a bug", "create a task", "add to backlog", or invokes /compass-rose:add-item. Replaces /lore-development:file-issue. Creates a local issue file in .lore/work/issues/.
What this skill does
# Add Item Gather the details, write the issue file, confirm. No GitHub API, no config file, no authentication. ## Step 1: Qualify the observation If the user's input is too vague to write up clearly, say so and stop. Do not file a placeholder. ## Step 2: Gather details Ask for the following, in order. Skip any field the user doesn't answer. **Title** (required): A short, clear label for the issue. Used as the filename. **Description** (optional): What's happening, why it matters, fix direction if known. **Priority** (optional): P0 / P1 / P2 / P3. No default. Skip if the user doesn't know. **Size** (optional): S / M / L / XL. No default. Skip if the user doesn't know. Do not prompt for status. Status is always `open`. Do not prompt about XL escalation. That behavior is retired. ## Step 3: Create the issue file Derive the filename from the title: lowercase, spaces to hyphens, strip punctuation. Path: `.lore/work/issues/[kebab-case-title].html` Create the directory if it doesn't exist. ### File format Standard HTML. Meta tags in `<head>` carry the structured fields. Body carries the human-readable content. **Required meta tags:** - `date` — today's date, YYYY-MM-DD - `status` — always `open` - `tags` — inferred from content (comma-separated) **Conditional meta tags (omit if not provided):** - `priority` — P0 / P1 / P2 / P3 - `size` — S / M / L / XL **Body must include:** - A visible status badge (e.g. `<span class="badge">open</span>`) - A priority indicator if priority was set - The observation, why it matters, and fix direction if known Inline CSS is fine. No external dependencies. **Example meta block:** ```html <meta name="date" content="2026-05-20"> <meta name="status" content="open"> <meta name="tags" content="bug, auth"> <meta name="priority" content="P1"> <meta name="size" content="S"> ``` ## Step 4: Confirm and stop Tell the user the file was created and where it lives. Then stop — do not start working the issue. ## Related skills - `/compass-rose:next-item` — find the next issue to work - `/compass-rose:backlog` — review all open issues - `/lore-development:specify` — write a formal spec for larger items
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.