メニュー
Creates and manages issues via tissue for tracking work items, bugs, and features. Use for organizing work, checking ready issues, or updating status.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ForceInjection/domain-driven-design-skills --skill issue-trackingコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Conduct deep academic research for philosophy, neuroscience, cognitive science, and theoretical computer science (computability, complexity, AI theory, logic). Use when user asks to: research academic topics, find scholarly papers, conduct literature reviews, analyze citations, synthesize research findings, explore philosophical arguments, investigate consciousness/cognition, study computability/decidability/Turing machines, or analyze academic debates. Triggers on: 'research papers', 'literature review', 'academic sources', 'scholarly articles', 'philosophy of mind', 'computability theory', 'neuroscience studies', 'find papers on', 'what does the research say'.
Create clear action plans with steps, success criteria, and risk awareness. Use before implementing features, making changes, starting projects, or anytime you need a roadmap to success. Triggers on "plan this", "how should we approach", "what's the strategy", "steps to complete", or when facing complex multi-step work.
Add keyboard navigation to a feature using CommandRegistryService. Use when implementing keyboard shortcuts, vim-style navigation, or hotkeys for a page or component.
SOC 職業分類に基づく
SKILL.md を表示中
| name | issue-tracking |
| description | Creates and manages issues via tissue for tracking work items, bugs, and features. Use for organizing work, checking ready issues, or updating status. |
Work tracking via tissue, a git-native issue tracker.
Tissue stores issues in .tissue/ (git-tracked).
# Initialize (once per project)
tissue init
tissue list # All issues
tissue list --status open # Open only
tissue list --tag bug # By tag
tissue list --priority 1 # High priority
tissue ready # No blockers, ready to work
tissue show <id>
tissue new "title"
tissue new "title" -t bug # With tag
tissue new "title" -p 1 # Priority 1 (highest)
tissue new "title" -t feature -p 2 # Both
tissue status <id> open
tissue status <id> in_progress
tissue status <id> closed
tissue comment <id> -m "message"
| Tag | Purpose |
|---|---|
bug | Something broken |
feature | New functionality |
refactor | Code improvement |
docs | Documentation |
trivial | Quick fix |
| Priority | Meaning |
|---|---|
| 1 | Critical - do first |
| 2 | High - do soon |
| 3 | Medium - normal |
| 4 | Low - when time permits |
| 5 | Backlog - someday |
# Add dependency (A blocks B)
tissue dep add <blocker-id> blocks <blocked-id>
# Remove dependency
tissue dep rm <blocker-id> blocks <blocked-id>
# Show what blocks an issue
tissue show <id> # Lists blockers
Use tissue to track work items. When working on an issue:
tissue ready to see what's availabletissue status <id> in_progresstissue status <id> closedIssues get IDs like auth-a3f2. The prefix comes from the title:
auth-xxxxcaching-xxxx# Create a bug
tissue new "Login fails on Safari" -t bug -p 2
# Check ready work
tissue ready
# Start working
tissue status auth-a3f2 in_progress
# Add finding
tissue comment auth-a3f2 -m "Root cause: cookie SameSite attribute"
# Close it
tissue status auth-a3f2 closed
# High priority bugs
tissue list --tag bug --priority 1
# All open features
tissue list --tag feature --status open
# Everything assigned to current sprint
tissue list --tag sprint-42
Issue topics in jwz follow the pattern issue:<id>:
# Post to issue topic
jwz post "issue:auth-a3f2" -m "Starting work on this"
# Read issue discussion
jwz read "issue:auth-a3f2"
This connects tissue issues with agent discussions.