メニュー
Use when the user asks to "reprioritize", "update priorities", "scan codebase for relevance", or invokes /compass-rose:reprioritize. Scans codebase against local issue files and updates their priority/status meta tags.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/rjroy/vibe-garden --skill reprioritizeコマンドは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 | reprioritize |
| description | Use when the user asks to "reprioritize", "update priorities", "scan codebase for relevance", or invokes /compass-rose:reprioritize. Scans codebase against local issue files and updates their priority/status meta tags. |
| allowed-tools | Bash, Read, Glob, Edit, Agent |
You are now in Reprioritize Mode. Your role is to analyze the current codebase state against local issue files and provide data-driven priority change recommendations. You identify issues that may be resolved, outdated, more urgent, or more feasible based on recent code changes.
.lore/work/issues/*.htmlcodebase-scanner agent to assess relevanceUse Glob to find all HTML files under .lore/work/issues/:
find .lore/work/issues -name "*.html" 2>/dev/null
For each file found, use Read to extract the meta tags and body content. The relevant tags are:
<meta name="title" content=>
Filter to only files where <meta name="status" content="open">.
If no open issues exist:
No open issues found in .lore/work/issues/.
Nothing to reprioritize.
Stop here.
If a large set is detected (>50 open issues):
Large backlog detected: [N] open issues to analyze.
This may take 5-10 minutes. Continue? (y/n)
Wait for confirmation before proceeding.
Build a JSON array from the parsed issue files and pass it to the codebase-scanner agent:
Agent Input Format:
{
"items": [
{
"filepath": ".lore/work/issues/fix-login-timeout.html",
"title": "Fix login timeout",
"body": "Users experiencing timeouts after 30 seconds...",
"priority": "P1",
"size": "M",
"status": "open",
"date": "2026-05-01"
}
]
}
Agent Invocation:
You are the codebase-scanner agent. Analyze the codebase and assess the relevance of these local issues:
[JSON data]
Follow the codebase-scanner agent protocol defined in compass-rose/agents/codebase-scanner.md.
Explore the codebase structure, check recent git activity, and analyze each issue to determine if:
- Feature already exists (recommend status: resolved)
- Issue is outdated or superseded (recommend lowering priority)
- Issue is more urgent due to recent changes (recommend raising priority)
- Issue is more feasible due to completed prerequisites (recommend raising priority or status: ready)
- Issue remains valid as-is (no change)
Return a structured markdown report with recommendations, confidence levels, and codebase evidence.
Expected Output: Structured markdown report following the format defined in codebase-scanner.md.
Display the agent's findings:
## Reprioritization Analysis Complete
**Issues Analyzed**: 25
**Recommendations**: 10 changes proposed
### Summary
- **Increase Priority**: 2 issues (prerequisites now met)
- **Decrease Priority**: 4 issues (less urgent than before)
- **Mark Resolved**: 3 issues (feature already implemented)
- **No Change**: 16 issues (remain valid as-is)
### High Confidence Changes (7 items)
| File | Current | Recommended | Rationale |
|------|---------|-------------|-----------|
| fix-login-timeout.html | P1 | resolved | Feature implemented in auth/login.ts (commit abc123, 2025-11-15) |
| add-oauth-support.html | P2 | P0 | Auth system refactored, OAuth integration now feasible |
| migrate-to-postgresql.html | P1 | P3 | DB abstraction added, migration no longer urgent |
### Medium Confidence Changes (3 items)
| File | Current | Recommended | Rationale |
|------|---------|-------------|-----------|
| improve-error-handling.html | P2 | P1 | Error handling recently modified in 5 files, consistency important |
**Note**: Medium confidence recommendations should be reviewed before applying.
---
## Detailed Findings
### fix-login-timeout.html
**Current Priority**: P1
**Recommended**: status → resolved
**Confidence**: High
**Codebase Evidence**:
- File `src/auth/login.ts` added 2025-11-15
- Contains timeout handling implementation (lines 45-67)
- Tests cover timeout scenarios (`tests/auth/login.test.ts`)
- Recent commit: "Add session timeout handling" (commit abc123)
**Rationale**: The feature described in this issue is fully implemented with test coverage.
[... continue for each recommendation ...]
---
Would you like to proceed with these changes?
Options:
1. **Apply all high confidence changes** ([N] items)
2. **Review and select specific changes** (show checklist)
3. **Cancel** (no changes made)
Enter choice (1/2/3):
For Option 1: apply all high confidence changes. For Option 2: show a checklist of all recommended changes; apply only the ones the user selects. For Option 3: exit without changes.
For each approved change, use the Edit tool to update the relevant meta tag in the target HTML file.
Priority update example (changing priority to P0 in fix-login-timeout.html):
Update the content attribute of <meta name="priority" content="..."> to the new value.
Status update example (marking as resolved):
Update the content attribute of <meta name="status" content="open"> to resolved.
After applying all changes, show a summary:
## Reprioritization Complete
**Issues Analyzed**: 25
**Updates Applied**: 7 items changed
### Changes Applied
- **Priority Increased**: 2 issues
- add-oauth-support.html (P2 -> P0)
- **Priority Decreased**: 4 issues
- migrate-to-postgresql.html (P1 -> P3)
- refactor-authentication.html (P1 -> P2)
- add-caching-layer.html (P2 -> P3)
- update-documentation.html (P1 -> P2)
- **Marked Resolved**: 1 issue
- fix-login-timeout.html
- **No Change**: 18 issues remain at current priority
**Next Steps**:
- View open issues: `/compass-rose:backlog`
## Reprioritization Analysis Complete
**Issues Analyzed**: 25
**Recommendations**: No changes needed
All issues remain relevant at their current priorities. The codebase state aligns well with the current backlog.
**Next Steps**:
- Continue with current priorities: `/compass-rose:next-item`
- Review backlog for definition quality: `/compass-rose:backlog`
Warning: Not a git repository or git unavailable.
The codebase scanner requires git history to assess issue relevance based on recent activity. Running in limited mode with feature existence checks only.
Continue with limited analysis? (y/n)
If the user continues, the agent skips git-based analysis and focuses on feature existence checks only.
/compass-rose:next-item - View highest priority ready item after reprioritization/compass-rose:backlog - Review backlog for definition quality/compass-rose:add-item - Create a new issue file