josephgoksu/taskwing/taskwing-context

Project Context Dump

Load the project knowledge base into this conversation for architectural context.

When to Use

• At the start of a session when you need to understand the project before making changes
• When the user says "what do you know about this project"
• When you need to check constraints before implementing something
• When planning work that touches multiple parts of the codebase

Kill Table

Operating Principles

1. Constraints first. Always present constraints before decisions and patterns. They are mandatory rules.
2. Decisions second. Technology and architecture choices frame the project.
3. Patterns third. Recurring practices inform how to write code in this project.

Steps

1. Run the CLI to dump all knowledge as JSON:

taskwing knowledge

1. Present the returned knowledge verbatim. The response is organized by type (constraints, decisions, patterns, features).

1. After presenting, confirm: "Project context loaded. I now have full visibility into your architecture. What would you like to work on?"

Filtered Lookups

For a single type:

taskwing knowledge constraint
taskwing knowledge decision
taskwing knowledge pattern

For a focused semantic query rather than a full dump:

taskwing ask "auth patterns"
taskwing ask "vectorsearch decisions" --limit 10

Important

• This is a READ-ONLY operation. It does not modify the knowledge base.
• If taskwing knowledge reports no nodes, tell the user to run taskwing learn first.
• Do NOT summarize or filter the results. Show everything so the user can verify.