| name | task-to-knowledge |
| description | Extract learnings from completed tasks and create knowledge notes. Use when user says "make this knowledge", "extract learnings", "save what I learned", or wants to convert task insights to permanent notes. |
Task to Knowledge
Extracts learnings from completed tasks and creates permanent knowledge notes.
When to Use
- Task is completed and has valuable insights
- User wants to save learnings for future reference
- Converting project experience to reusable knowledge
Process
- Read the completed task file
- Identify key learnings, patterns, or insights
- Create knowledge note in
Knowledge/
- Link back to source task
- Suggest related knowledge notes
- Move original task to
Archive/ (optional)
Knowledge Note Template
---
title: "Knowledge title"
type: knowledge
created: YYYY-MM-DD
source: [[task-filename]]
tags: [relevant, tags]
---
## Summary
Brief overview of the knowledge.
## Key Points
- Point 1
- Point 2
- Point 3
## Details
Detailed explanation if needed.
## Related
- [[related-knowledge-1]]
- [[related-knowledge-2]]
Extraction Guidelines
What to Extract
- Patterns: Reusable approaches or solutions
- Decisions: Why certain choices were made
- Gotchas: Problems encountered and how to avoid them
- Best Practices: Recommended ways of doing things
- References: Useful resources discovered
How to Name Knowledge Files
- Use descriptive kebab-case names
- Focus on the concept, not the task
- Examples:
- Task: "API認証実装" → Knowledge:
jwt-refresh-token-pattern.md
- Task: "チーム会議準備" → Knowledge:
effective-meeting-facilitation.md
Interactive Flow
- Show task content summary
- Ask: "What are the key learnings from this task?"
- Suggest knowledge title based on content
- Create draft knowledge note
- Ask for confirmation/edits
- Save to
Knowledge/
- Ask: "Move original task to Archive?"
Linking
- Add
source: [[task-id]] to knowledge frontmatter
- This preserves the connection to original context
- Enables tracing knowledge back to experience
Output
After creating knowledge:
Created: Knowledge/jwt-refresh-token-pattern.md
Key points captured:
- JWTは短命トークン(15分)推奨
- リフレッシュトークンはHTTPOnlyクッキーに保存
- ローテーション戦略でセキュリティ向上
Source: [[task-api-auth-implementation]]
Related notes found:
- [[api-security-basics]]
- [[authentication-patterns]]
Move original task to Archive? (y/n)