メニュー
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/.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/rjroy/vibe-garden --skill add-itemコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when extracting knowledge from .lore/ artifacts into the reference wiki. Converts work artifacts (retros, specs, plans, research, notes) into structured wiki pages grouped by knowledge type. Reads Markdown or HTML sources and writes Markdown by default. Triggers include "ingest this", "extract knowledge from", "add this to the wiki", "update the reference from", and "populate the field guide".
This skill is used when the project wiki needs a health check. Triggers include 'lint the wiki', 'check wiki health', 'run field-guide lint', 'are there stale wiki pages', 'find orphaned pages', 'check for contradictions in the wiki'.
Use when asking questions about the project wiki, querying accumulated knowledge, searching project decisions or lessons. Triggers include "query the wiki", "what does the wiki say about", "search project knowledge", and natural language questions directed at the field-guide wiki.
SKILL.md を表示中
SOC 職業分類に基づく
| name | add-item |
| description | 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/. |
| allowed-tools | Bash, Read, Write |
Gather the details, write the issue file, confirm. No GitHub API, no config file, no authentication.
If the user's input is too vague to write up clearly, say so and stop. Do not file a placeholder.
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.
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.
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-DDstatus — always opentags — inferred from content (comma-separated)Conditional meta tags (omit if not provided):
priority — P0 / P1 / P2 / P3size — S / M / L / XLBody must include:
<span class="badge">open</span>)Inline CSS is fine. No external dependencies.
Example meta block:
<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">
Tell the user the file was created and where it lives. Then stop — do not start working the issue.
/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