Full Tasuku Context Dump

VerifiedSafe

Extracts complete project context including tasks, learnings, and decisions for AI agent consumption.

Sby Skills Guide Bot
ProductivityBeginner
306/2/2026
Claude CodeCursorWindsurf
#task-management#context-dump#tasuku#project-state

Recommended for

Our review

This skill dumps the full Tasuku context (task state, decisions, learnings) for the agent, triggered by /tk:context or a request for project context.

Strengths

  • Provides a complete, structured overview of the project state
  • Highlights in-progress, blocked, and priority tasks
  • Includes recent decisions and learned rules

Limitations

  • Relies on an up-to-date .tasuku.json file
  • Can become lengthy in large projects with many tasks
When to use it

At the start of a work session to quickly reorient on the project's status

When not to use it

When you need details about a single task, use a targeted command instead.

Security analysis

Safe
Quality score85/100

This skill only reads and formats local project state data using an internal MCP tool; it does not execute any dangerous commands or exfiltrate data.

No concerns found

Examples

Full context dump
/tk:context
Request project state
Show me the current project context with all tasks and decisions.

name: tk-context description: Dump full Tasuku context for agent consumption. Use when user says /tk:context or asks for full context, project state, or needs to understand the entire task landscape.

Full Context Dump

Provide complete project context including all tasks, learnings, decisions, and notes.

Instructions

  1. Use the tk_context MCP tool to get the full .tasuku.json state
  2. Present the information in a structured, scannable format
  3. Highlight key items:
    • Tasks currently in progress (what's being worked on)
    • Blocked tasks and their blockers
    • Recent decisions that affect current work
    • Relevant learnings/rules

Output Format

## Current Work
[List in_progress tasks with owner if set]

## Ready Queue
[List ready tasks sorted by priority]

## Blockers
[List blocked tasks and what's blocking them]

## Key Decisions
[Recent or relevant architectural decisions]

## Learnings & Rules
[Important insights, especially any marked as rules]

## Notes
[Any notes attached to active tasks]

Notes

  • This is meant for getting oriented at the start of a session
  • Focus on actionable information
  • Skip archived tasks unless specifically requested
  • If context is large, summarize done tasks as a count
Related skills