em-jones/td-task-management
.agents/skills/td-task-management/SKILL.md
Task management for agents. Use for gaining and sharing information about work to complete.
$ install --global
skillsauthnpx skillsauth add em-jones/staccato-toolkit td-task-managementInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 5:15 AM6.8s7 files scanned
SKILL.md
- name:
- td-task-management
- description:
- Task management for agents. Use for gaining and sharing information about work to complete.
Overview
Use td to:
- Know what work to complete
- Track and Navigate work dependencies
- Track progress and decisions
- Discover relevant context for resuming work
When your session ends, use td to capture:
- work completed
- work remaining
- decisions made
This provides the next session with what it needs to continue.
Core capability: Run td usage and get everything needed for the next action:
- current focus
- pending reviews
- open issues
- recent decisions
Goal
Perform work as described by assigned tasks and track progress and decisions until a task is "closed."
stateDiagram-v2
open --> in_progress : start
in_progress --> in_review : submit
in_progress --> blocked : block
in_review --> closed : approve
in_review --> in_progress : reject
Patterns
ALWAYS apply these patterns when the situation calls for it:
- Always start with
td usage --new-session- Tells you current focus, pending reviews, and what to work on - Handoff before context ends - Don't let context window expire without handoff
- Use work sessions for related issues - Groups handoffs and makes tracking easier
- Check blockers vs openwork - If blocked, don't waste tokens retrying - work on something else
- Log Progress:
- Log decisions → Use
--decisionflag to mark decisions - Log uncertainty → Use
--uncertainflag to mark unknowns - Log log attempted approach → Use
--triedflag to mark unknowns - Log hypothesis → Use
--hypothesisflag to mark hypotheses - Log results → Use
--resultflag to mark results of an approach
- Log decisions → Use
- Track files → Use
td linkso future sessions know what changed - Link reference → Use
td linkto link task to files for reference purposes, like associated specs, docs, rules, or code
Workflow
When starting work
Get highest priority open issue : td next
Determine what unblocks most work: td critical-path
- Signle issue workflow
- Multi issue workflow
ALWAYS apply these patterns for the common workflows and scenarios you'll encounter. IMPORTANT: only refer to linked documents for the workflow relevant to your current progress.
- delegating work or ending a session: reference
- reviewing work: reference
- handling blockers: reference
See quick reference for a summary of common commands.
Related Skills
em-jones/.agents/skills/vite-plus
tools
VerifiedTrustedCommunity
<!--VITE PLUS START--> # Using Vite+, the Unified Toolchain for the Web This project is using Vite+, a unified toolchain built on top of Vite, Rolldown, Vitest, tsdown, Oxlint, Oxfmt, and Vite Task. Vite+ wraps runtime management, package management, and frontend tooling in a single global CLI called `vp`. Vite+ is distinct from Vite, but it invokes Vite through `vp dev` and `vp build`. ## Vite+ Workflow `vp` is a global binary that handles the full development lifecycle. Run `vp help` to pr
1SKILL.mdUpdated Apr 17, 2026
em-jones/ui-data-tables
development
VerifiedTrustedCommunity
Guide for building performant data tables. Uses tanstack-table for table logic (sorting, filtering, pagination) and tanstack-virtual for rendering large datasets efficiently.
1SKILL.mdUpdated Apr 17, 2026
em-jones/typescript-effect-library
development
VerifiedTrustedCommunity
Expert guidance for building observable, expressive, and fault-tolerant TypeScript applications using the effect-ts/effect ecosystem. Covers Effect<A, E, R> type, error management, dependency injection via Layers, observability (logging, metrics, tracing), concurrency with Fibers, retry/scheduling, Schema validation, Streams, and Sinks.
1SKILL.mdUpdated Apr 17, 2026
em-jones/typescript-e2e-testing
tools
VerifiedTrustedCommunity
Complete E2E (end-to-end) and integration testing skill for TypeScript/NestJS projects using Jest, real infrastructure via Docker, and GWT pattern. ALWAYS use this skill when user needs to: **SETUP** - Initialize or configure E2E testing infrastructure: - Set up E2E testing for a new project - Configure docker-compose for testing (Kafka, PostgreSQL, MongoDB, Redis) - Create jest-e2e.config.ts or E2E Jest configuration - Set up test helpers for database, Kafka, or Redis - Configure .env.e2e environment variables - Create test/e2e directory structure **WRITE** - Create or add E2E/integration tests: - Write, create, add, or generate e2e tests or integration tests - Test API endpoints, workflows, or complete features end-to-end - Test with real databases, message brokers, or external services - Test Kafka consumers/producers, event-driven workflows - Working on any file ending in .e2e-spec.ts or in test/e2e/ directory - Use GWT (Given-When-Then) pattern for tests **REVIEW** - Audit or evaluate E2E tests: - Review existing E2E tests for quality - Check test isolation and cleanup patterns - Audit GWT pattern compliance - Evaluate assertion quality and specificity - Check for anti-patterns (multiple WHEN actions, conditional assertions) **RUN** - Execute or analyze E2E test results: - Run E2E tests - Start/stop Docker infrastructure for testing - Analyze E2E test results - Verify Docker services are healthy - Interpret test output and failures **DEBUG** - Fix failing or flaky E2E tests: - Fix failing E2E tests - Debug flaky tests or test isolation issues - Troubleshoot connection errors (database, Kafka, Redis) - Fix timeout issues or async operation failures - Diagnose race conditions or state leakage - Debug Kafka message consumption issues **OPTIMIZE** - Improve E2E test performance: - Speed up slow E2E tests - Optimize Docker infrastructure startup - Replace fixed waits with smart polling - Reduce beforeEach cleanup time - Improve test parallelization where safe Keywords: e2e, end-to-end, integration test, e2e-spec.ts, test/e2e, Jest, supertest, NestJS, Kafka, Redpanda, PostgreSQL, MongoDB, Redis, docker-compose, GWT pattern, Given-When-Then, real infrastructure, test isolation, flaky test, MSW, nock, waitForMessages, fix e2e, debug e2e, run e2e, review e2e, optimize e2e, setup e2e
1SKILL.mdUpdated Apr 17, 2026