[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PEYTYK4A74WHF7H5520WYP":3,"skill-same:01M6PEYTYK4A74WHF7H5520WYP":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6PEYTYK4A74WHF7H5520WYP","001-jeremy-taskwarrior-integration",null,"Enforces complete Taskwarrior integration protocol for ALL coding tasks. Activates automatically when user mentions \"taskwarrior\", \"task warrior\", \"tw\", or discusses task management. Decomposes all coding work into properly tracked Taskwarrior tasks with full lifecycle: task add → task start → implementation → task done. Integrates with Timewarrior for automatic time tracking.","sandraschi\u002Fdocumentation-mcp","sandraschi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34750307?v=4","01M6C42H9WE5EC9CK3N5RGZP8S","Sandra Schipal","01M6PE1X2FZP8KR5GANPPFTHA8",2,"MIT","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fproductivity\u002F001-jeremy-taskwarrior-integration\u002Fskills\u002F001-jeremy-taskwarrior-integration\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"integration","001 jeremy taskwarrior integration","taskwarrior","automatic","tasks","for","time tracking","add","complete","full","time","done","task","task done","task add","work","coding","task management","lifecycle","start","2026-11-10 10:12:30",false,"---\nname: 001-jeremy-taskwarrior-integration\ndescription: |\n  Enforces complete Taskwarrior integration protocol for ALL coding tasks. Activates automatically when user mentions \"taskwarrior\", \"task warrior\", \"tw\", or discusses task management. Decomposes all coding work into properly tracked Taskwarrior tasks with full lifecycle: task add → task start → implementation → task done. Integrates with Timewarrior for automatic time tracking.\n---\n\n## What This Skill Does\n\nThis skill **enforces mandatory Taskwarrior integration** for ALL coding activities. It ensures every piece of work is:\n\n1. **Decomposed** into trackable Taskwarrior tasks BEFORE code is written\n2. **Tracked** with proper attributes (project, priority, due date, tags)\n3. **Time-accounted** via automatic Timewarrior integration\n4. **Dependency-managed** for complex multi-step projects\n5. **Completed** with proper task lifecycle (add → start → done)\n\n**CRITICAL: NO CODE IS WRITTEN until Taskwarrior tasks are created and started.**\n\n## When This Skill Activates\n\nTrigger this skill when you mention:\n- \"taskwarrior\"\n- \"task warrior\"\n- \"tw\" (as abbreviation)\n- \"create a task for this\"\n- \"track this work\"\n- \"add to taskwarrior\"\n- \"start a task\"\n- \"task management\"\n- \"time tracking\"\n\n## Complete Taskwarrior Integration Protocol\n\n### Phase 1: Task Decomposition (MANDATORY FIRST STEP)\n\n**Before writing ANY code**, decompose the request into Taskwarrior tasks:\n\n**For Simple Requests (1 task):**\n```bash\ntask add \"Brief description of work\" project:ProjectName priority:H\u002FM\u002FL due:today\u002Ftomorrow\u002FYYYY-MM-DD +tag1 +tag2\n```\n\n**For Complex Requests (multiple tasks with dependencies):**\n```bash\n# Parent task\ntask add \"Main project goal\" project:ProjectName priority:H due:3days +architecture +planning\n\n# Subtasks with dependencies\ntask add \"Subtask 1\" project:ProjectName depends:1 priority:M +implementation\ntask add \"Subtask 2\" project:ProjectName depends:2 priority:M +testing\ntask add \"Subtask 3\" project:ProjectName depends:3 priority:L +documentation\n```\n\n**Required Task Attributes:**\n- **project:** Categorize the work (e.g., project:DevOps, project:WebDev)\n- **priority:** H (high), M (medium), or L (low) based on urgency\n- **due:** Realistic deadline (today, tomorrow, YYYY-MM-DD, or relative like 3days)\n- **tags:** At least 2 relevant tags (+feature, +bugfix, +refactor, +testing, +deployment, +security, etc.)\n\n### Phase 2: Task Activation & Time Tracking\n\n**After creating tasks**, activate them to start time tracking:\n\n```bash\n# Start the first task in the dependency chain\ntask \u003CID> start\n\n# Verify task is active\ntask active\n\n# Timewarrior should automatically begin tracking\ntimew\n```\n\n**What happens:**\n- Taskwarrior marks task as started\n- Timewarrior begins tracking time spent\n- Task appears in `task active` list\n- Urgency score increases for started tasks\n\n### Phase 3: Code Implementation\n\n**Now and ONLY now** proceed with writing code:\n\n1. Implement the solution following best practices\n2. Annotate task with key decisions or blockers:\n```bash\ntask \u003CID> annotate \"Decision: Using FastAPI over Flask for async support\"\ntask \u003CID> annotate \"Blocker: Waiting for API credentials\"\n```\n\n3. If blocked, stop the task temporarily:\n```bash\ntask \u003CID> stop\ntask \u003CID> modify +blocked\n```\n\n4. If scope changes mid-implementation:\n```bash\ntask \u003CID> modify +additional_tag description:\"Updated description\"\n```\n\n### Phase 4: Task Completion\n\n**After code is delivered and verified**, complete the task:\n\n```bash\n# Complete the task\ntask \u003CID> done\n\n# Timewarrior automatically stops tracking\n# View time summary for this task\ntimew summary :ids\n\n# Check if dependent tasks are now unblocked\ntask next\n```\n\n**Completion Checklist:**\n- ✅ Code is written and tested\n- ✅ Documentation is updated (if applicable)\n- ✅ Task annotations reflect final state\n- ✅ Any blockers are resolved or escalated\n- ✅ Time tracking is accurate\n\n### Phase 5: Verification & Reporting\n\n**After completing tasks**, provide summary:\n\n```bash\n# Show completed task details\ntask \u003CID> info\n\n# Show time spent\ntimew summary :ids\n\n# Show remaining work\ntask next\n```\n\n## Task Decomposition Examples\n\n### Example 1: Simple Single-File Script\n\n**User Request:** \"Create a Bash script that backs up my home directory\"\n\n**Task Decomposition:**\n```bash\ntask add \"Create home directory backup script\" project:DevOps priority:M due:today +scripting +automation +backup\n```\n\n**Lifecycle:**\n```bash\ntask 42 start\n[Write backup.sh script]\ntask 42 done\ntimew summary :ids\n```\n\n### Example 2: Complex Multi-Component Feature\n\n**User Request:** \"Build a REST API with authentication, user management, and PostgreSQL\"\n\n**Task Decomposition:**\n```bash\n# Parent task\ntask add \"Build FastAPI REST API with auth\" project:WebDev priority:H due:5days +api +backend\n\n# Dependent subtasks\ntask add \"Design PostgreSQL schema\" project:WebDev depends:43 priority:H due:1day +database +design\ntask add \"Implement JWT authentication\" project:WebDev depends:44 priority:H due:2days +auth +security\ntask add \"Create user management endpoints\" project:WebDev depends:45 priority:M due:3days +crud +endpoints\ntask add \"Write API documentation\" project:WebDev depends:46 priority:L due:5days +documentation +openapi\ntask add \"Deploy to staging environment\" project:WebDev depends:47 priority:M due:5days +deployment +staging\n```\n\n**Lifecycle:**\n```bash\ntask 44 start  # Start with database schema\n[Design and implement schema]\ntask 44 done\n\ntask 45 start  # Next: authentication\n[Implement JWT auth]\ntask 45 done\n\n# Continue through dependency chain...\n```\n\n### Example 3: Debugging Investigation\n\n**User Request:** \"My Node.js app crashes with ECONNREFUSED\"\n\n**Task Decomposition:**\n```bash\ntask add \"Debug ECONNREFUSED error in Node.js app\" project:Debugging priority:H due:today +debugging +nodejs +urgent +investigation\n```\n\n**Lifecycle with Annotations:**\n```bash\ntask 50 start\ntask 50 annotate \"Error occurs during PostgreSQL connection\"\ntask 50 annotate \"Root cause: PostgreSQL service not running\"\ntask 50 annotate \"Solution: systemctl start postgresql\"\n[Provide debugging steps and code fixes]\ntask 50 done\n```\n\n### Example 4: Recurring Maintenance Task\n\n**User Request:** \"Create a script I need to run weekly to clean Docker images\"\n\n**Task Decomposition:**\n```bash\ntask add \"Weekly Docker cleanup script\" project:Maintenance recur:weekly due:friday priority:M +automation +docker +cleanup\n```\n\n**Lifecycle:**\n```bash\ntask 55 start\n[Write docker-cleanup.sh script]\ntask 55 done\n\n# Future instances auto-generate every Friday\ntask next  # Will show next week's instance\n```\n\n## Task Priority Guidelines\n\nUse this urgency matrix to assign priority:\n\n**priority:H (High) - Use when:**\n- Blocking other work\n- Production outage or critical bug\n- Security vulnerability\n- Hard deadline within 24-48 hours\n- Explicitly marked as urgent by user\n\n**priority:M (Medium) - Use when:**\n- Normal feature development\n- Non-blocking improvements\n- Deadline within 3-7 days\n- Standard maintenance work\n- Default for most tasks\n\n**priority:L (Low) - Use when:**\n- Nice-to-have enhancements\n- Documentation updates\n- Refactoring for cleanliness (not performance)\n- No specific deadline\n- Can be deferred without impact\n\n## Tag Taxonomy\n\n**Common Project Tags:**\n- `+feature` - New functionality\n- `+bugfix` - Fixing existing issues\n- `+refactor` - Code restructuring\n- `+testing` - Test creation\u002Fexecution\n- `+documentation` - Docs and comments\n- `+deployment` - Release and infrastructure\n- `+security` - Security-related work\n- `+performance` - Optimization work\n- `+debugging` - Investigation and diagnosis\n- `+maintenance` - Routine upkeep\n- `+automation` - Scripting and tooling\n- `+infrastructure` - DevOps and systems\n\n**Technology Tags:**\n- `+python`, `+javascript`, `+bash`, `+typescript`\n- `+docker`, `+kubernetes`, `+cicd`\n- `+postgresql`, `+redis`, `+mongodb`\n- `+fastapi`, `+react`, `+nextjs`\n\n**Status Tags:**\n- `+blocked` - Cannot proceed (annotate reason)\n- `+urgent` - Needs immediate attention\n- `+waiting` - Awaiting external input\n- `+review` - Ready for review\n\n## Handling Special Scenarios\n\n### Scenario 1: Mid-Task Scope Change\n\nIf requirements change while working:\n\n```bash\n# Modify existing task\ntask \u003CID> modify +new_tag description:\"Updated description\"\n\n# Or create dependent subtask for additional work\ntask add \"Additional scope: Email notifications\" depends:\u003CID> project:SameProject +feature\n```\n\n### Scenario 2: Blocked Work\n\nIf encountering blockers (missing credentials, API limits, permissions):\n\n```bash\n# Stop the task\ntask \u003CID> stop\n\n# Annotate the blocker\ntask \u003CID> annotate \"Blocked: Need AWS credentials from ops team\"\n\n# Mark as blocked\ntask \u003CID> modify +blocked\n\n# Explain to user what's needed to unblock\n```\n\n### Scenario 3: Multi-Session Work\n\nFor work spanning multiple conversations:\n\n**Session 1:**\n```bash\ntask add \"Build e-commerce platform - product catalog\" project:Ecommerce priority:H +feature\ntask 60 start\n[Implement product catalog]\ntask 60 done\n```\n\n**Session 2 (later):**\n```bash\n# Check existing project tasks\ntask project:Ecommerce status:pending\n\n# Create related task\ntask add \"Build e-commerce platform - shopping cart\" project:Ecommerce depends:60 priority:H +feature\ntask 61 start\n[Implement shopping cart]\ntask 61 done\n```\n\n### Scenario 4: Working with User's Existing Tasks\n\nIf user references an existing Taskwarrior task:\n\n**User:** \"Help me complete task 42: 'Optimize database queries'\"\n\n**Response:**\n```bash\n# Start user's existing task\ntask 42 start\n\n[Provide optimization recommendations and code]\n\n# Complete user's task\ntask 42 done\n\n# Show results\ntask 42 info\ntimew summary :ids\n```\n\n## Integration with Timewarrior\n\nTaskwarrior automatically integrates with Timewarrior when configured. Here's what happens:\n\n**When you start a task:**\n```bash\ntask \u003CID> start\n# Timewarrior begins tracking with tags from the task\n```\n\n**Check current tracking:**\n```bash\ntimew  # Shows what's currently being tracked\ntask active  # Shows active Taskwarrior tasks\n```\n\n**Stop tracking (when you stop or complete a task):**\n```bash\ntask \u003CID> stop  # Pauses tracking\ntask \u003CID> done  # Stops tracking and completes task\n```\n\n**View time reports:**\n```bash\ntimew summary :ids              # Total time per task\ntimew report :ids :week         # This week's breakdown\ntimew tags                      # Most-used tags\ntimew day                       # Today's time usage\n```\n\n## Workflow Enforcement Rules\n\n### MANDATORY RULES:\n\n1. **NO CODE BEFORE TASKS** - Always run `task add` BEFORE writing any code\n2. **ALWAYS START TASKS** - Run `task \u003CID> start` to activate time tracking\n3. **ALWAYS COMPLETE TASKS** - Run `task \u003CID> done` when work is delivered\n4. **USE PROPER ATTRIBUTES** - Every task needs project:, priority:, due:, and tags:\n5. **RESPECT DEPENDENCIES** - Work tasks in order defined by `depends:` relationships\n6. **ANNOTATE DECISIONS** - Use `task \u003CID> annotate` to document key choices\n7. **HANDLE BLOCKERS EXPLICITLY** - Stop tasks and mark as +blocked when stuck\n\n### VERIFICATION CHECKLIST:\n\nBefore delivering code, confirm:\n- ✅ Task was created with proper attributes\n- ✅ Task was started (appears in `task active`)\n- ✅ Time tracking is running (verify with `timew`)\n- ✅ Code is implemented and tested\n- ✅ Task is completed with `task done`\n- ✅ Time summary is shown\n\n## Refusing Non-Compliant Requests\n\nIf user asks for code without mentioning Taskwarrior, **proactively enforce the protocol**:\n\n**User:** \"Write me a Python script to parse CSV files\"\n\n**Your Response:**\n```\nBefore I write the code, I need to create a Taskwarrior task to track this work properly.\n\nI'll decompose this as:\ntask add \"Create CSV parser Python script\" project:DataProcessing priority:M due:today +python +scripting +parsing\n\nThen I'll start the task and implement the solution.\n\n[Proceed with task creation → task start → code implementation → task done]\n```\n\n## Success Metrics\n\nAfter completing work, provide these metrics:\n\n```bash\n# Task details\ntask \u003CID> info\n\n# Time spent\ntimew summary :ids\n\n# Project progress\ntask project:\u003CProjectName> completed\ntask project:\u003CProjectName> status:pending\n\n# Personal productivity\ntask completed count\ntask active count\n```\n\n## Quick Reference Commands\n\n| Operation | Command |\n|-----------|---------|\n| **Create task** | `task add \"description\" project:Name priority:M due:today +tag1 +tag2` |\n| **Start task** | `task \u003CID> start` |\n| **Stop task** | `task \u003CID> stop` |\n| **Complete task** | `task \u003CID> done` |\n| **View active tasks** | `task active` |\n| **View next tasks** | `task next` |\n| **Modify task** | `task \u003CID> modify priority:H +new_tag` |\n| **Annotate task** | `task \u003CID> annotate \"note\"` |\n| **View task details** | `task \u003CID> info` |\n| **List by project** | `task project:ProjectName list` |\n| **Show time tracking** | `timew` |\n| **Time summary** | `timew summary :ids` |\n| **Weekly report** | `timew report :ids :week` |\n\n## Expected User Workflow\n\n**Typical Interaction:**\n\n**User:** \"I need help with taskwarrior - create a FastAPI authentication system\"\n\n**Your Response:**\n```\nI'll enforce the Taskwarrior integration protocol for this work.\n\n## Phase 1: Task Decomposition\n\nCreating tasks for FastAPI authentication system:\n\ntask add \"Build FastAPI authentication system\" project:WebDev priority:H due:2days +fastapi +auth +security +backend\ntask add \"Implement JWT token generation\" project:WebDev depends:1 priority:H +jwt +auth\ntask add \"Create login\u002Flogout endpoints\" project:WebDev depends:2 priority:M +endpoints +api\ntask add \"Add password hashing with bcrypt\" project:WebDev depends:3 priority:M +security +passwords\ntask add \"Write authentication tests\" project:WebDev depends:4 priority:M +testing +pytest\n\n## Phase 2: Task Activation\n\ntask 1 start\ntimew  # Verify tracking started\n\n## Phase 3: Implementation\n\n[Now I'll implement the authentication system...]\n\n[Provide complete FastAPI auth code]\n\n## Phase 4: Completion\n\ntask 1 done\ntimew summary :ids\n\nTotal time: 45 minutes\nNext task: Implement JWT token generation (task 2)\n```\n\n## Best Practices\n\n### ✅ DO:\n- Create tasks for EVERY coding activity, no matter how small\n- Use descriptive task names that explain the \"what\" and \"why\"\n- Set realistic due dates based on complexity\n- Add multiple relevant tags for better filtering\n- Annotate tasks with important decisions or blockers\n- Leverage the dependency system for related work\n- Complete tasks when work is done (don't leave tasks hanging)\n- Review `task next` regularly to prioritize work\n\n### ❌ DON'T:\n- Skip task creation for \"quick\" tasks\n- Write code before creating and starting tasks\n- Use generic descriptions (\"Fix bug\" vs. \"Fix OAuth redirect loop\")\n- Ignore the dependency system\n- Leave tasks incomplete after delivering code\n- Forget to stop\u002Fcomplete tasks when switching contexts\n- Use priority:H for everything (dilutes urgency)\n\n## Troubleshooting\n\n### Issue: \"Task not tracking time\"\n\n**Solution:**\n```bash\n# Verify Timewarrior is installed\nwhich timew\n\n# Check if task is active\ntask active\n\n# Manually start tracking if needed\ntimew start +tag1 +tag2\n```\n\n### Issue: \"Can't find task ID\"\n\n**Solution:**\n```bash\n# List all tasks\ntask list\n\n# Show task details by description search\ntask \u002Fkeyword\u002F list\n\n# Show recently completed tasks\ntask completed\n```\n\n### Issue: \"Forgot to start task before coding\"\n\n**Solution:**\n```bash\n# Start the task now (retroactively)\ntask \u003CID> start\n\n# Manually adjust Timewarrior if needed\ntimew track yesterday 2:00pm - 3:30pm +projecttag +featuretag\n```\n\n## Integration with Your Workflow\n\nThis skill integrates seamlessly with:\n- **VS Code Taskwarrior extensions** - See tasks in your editor sidebar\n- **CI\u002FCD pipelines** - Auto-create tasks for deployments\n- **Git workflows** - Reference task IDs in commit messages\n- **Team collaboration** - Shared Taskwarrior server for team visibility\n- **Reporting tools** - Export to JSON for dashboards\n\n## Summary\n\nThis skill enforces a **mandatory, comprehensive Taskwarrior integration** for ALL coding activities. It ensures:\n\n✅ Every piece of work is tracked as a task\n✅ Time spent is automatically accounted via Timewarrior\n✅ Complex projects are decomposed into manageable, linked subtasks\n✅ Complete audit trail of all work performed\n✅ Proper prioritization and deadline management\n✅ Full lifecycle from creation → activation → implementation → completion\n\n**NO CODE GETS WRITTEN without following the complete Taskwarrior protocol.**\n","## What This Skill Does\n\nThis skill **enforces mandatory Taskwarrior integration** for ALL coding activities. It ensures every piece of work is:\n\n1. **Decomposed** into trackable Taskwarrior tasks BEFORE code is written\n2. **Tracked** with proper attributes (project, priority, due date, tags)\n3. **Time-accounted** via automatic Timewarrior integration\n4. **Dependency-managed** for complex multi-step projects\n5. **Completed** with proper task lifecycle (add → start → done)\n\n**CRITICAL: NO CODE IS WRITTEN until Taskwarrior tasks are created and started.**\n\n## When This Skill Activates\n\nTrigger this skill when you mention:\n- \"taskwarrior\"\n- \"task warrior\"\n- \"tw\" (as abbreviation)\n- \"create a task for this\"\n- \"track this work\"\n- \"add to taskwarrior\"\n- \"start a task\"\n- \"task management\"\n- \"time tracking\"\n\n## Complete Taskwarrior Integration Protocol\n\n### Phase 1: Task Decomposition (MANDATORY FIRST STEP)\n\n**Before writing ANY code**, decompose the request into Taskwarrior tasks:\n\n**For Simple Requests (1 task):**\n```bash\ntask add \"Brief description of work\" project:ProjectName priority:H\u002FM\u002FL due:today\u002Ftomorrow\u002FYYYY-MM-DD +tag1 +tag2\n```\n\n**For Complex Requests (multiple tasks with dependencies):**\n```bash\n# Parent task\ntask add \"Main project goal\" project:ProjectName priority:H due:3days +architecture +planning\n\n# Subtasks with dependencies\ntask add \"Subtask 1\" project:ProjectName depends:1 priority:M +implementation\ntask add \"Subtask 2\" project:ProjectName depends:2 priority:M +testing\ntask add \"Subtask 3\" project:ProjectName depends:3 priority:L +documentation\n```\n\n**Required Task Attributes:**\n- **project:** Categorize the work (e.g., project:DevOps, project:WebDev)\n- **priority:** H (high), M (medium), or L (low) based on urgency\n- **due:** Realistic deadline (today, tomorrow, YYYY-MM-DD, or relative like 3days)\n- **tags:** At least 2 relevant tags (+feature, +bugfix, +refactor, +testing, +deployment, +security, etc.)\n\n### Phase 2: Task Activation & Time Tracking\n\n**After creating tasks**, activate them to start time tracking:\n\n```bash\n# Start the first task in the dependency chain\ntask \u003CID> start\n\n# Verify task is active\ntask active\n\n# Timewarrior should automatically begin tracking\ntimew\n```\n\n**What happens:**\n- Taskwarrior marks task as started\n- Timewarrior begins tracking time spent\n- Task appears in `task active` list\n- Urgency score increases for started tasks\n\n### Phase 3: Code Implementation\n\n**Now and ONLY now** proceed with writing code:\n\n1. Implement the solution following best practices\n2. Annotate task with key decisions or blockers:\n```bash\ntask \u003CID> annotate \"Decision: Using FastAPI over Flask for async support\"\ntask \u003CID> annotate \"Blocker: Waiting for API credentials\"\n```\n\n3. If blocked, stop the task temporarily:\n```bash\ntask \u003CID> stop\ntask \u003CID> modify +blocked\n```\n\n4. If scope changes mid-implementation:\n```bash\ntask \u003CID> modify +additional_tag description:\"Updated description\"\n```\n\n### Phase 4: Task Completion\n\n**After code is delivered and verified**, complete the task:\n\n```bash\n# Complete the task\ntask \u003CID> done\n\n# Timewarrior automatically stops tracking\n# View time summary for this task\ntimew summary :ids\n\n# Check if dependent tasks are now unblocked\ntask next\n```\n\n**Completion Checklist:**\n- ✅ Code is written and tested\n- ✅ Documentation is updated (if applicable)\n- ✅ Task annotations reflect final state\n- ✅ Any blockers are resolved or escalated\n- ✅ Time tracking is accurate\n\n### Phase 5: Verification & Reporting\n\n**After completing tasks**, provide summary:\n\n```bash\n# Show completed task details\ntask \u003CID> info\n\n# Show time spent\ntimew summary :ids\n\n# Show remaining work\ntask next\n```\n\n## Task Decomposition Examples\n\n### Example 1: Simple Single-File Script\n\n**User Request:** \"Create a Bash script that backs up my home directory\"\n\n**Task Decomposition:**\n```bash\ntask add \"Create home directory backup script\" project:DevOps priority:M due:today +scripting +automation +backup\n```\n\n**Lifecycle:**\n```bash\ntask 42 start\n[Write backup.sh script]\ntask 42 done\ntimew summary :ids\n```\n\n### Example 2: Complex Multi-Component Feature\n\n**User Request:** \"Build a REST API with authentication, user management, and PostgreSQL\"\n\n**Task Decomposition:**\n```bash\n# Parent task\ntask add \"Build FastAPI REST API with auth\" project:WebDev priority:H due:5days +api +backend\n\n# Dependent subtasks\ntask add \"Design PostgreSQL schema\" project:WebDev depends:43 priority:H due:1day +database +design\ntask add \"Implement JWT authentication\" project:WebDev depends:44 priority:H due:2days +auth +security\ntask add \"Create user management endpoints\" project:WebDev depends:45 priority:M due:3days +crud +endpoints\ntask add \"Write API documentation\" project:WebDev depends:46 priority:L due:5days +documentation +openapi\ntask add \"Deploy to staging environment\" project:WebDev depends:47 priority:M due:5days +deployment +staging\n```\n\n**Lifecycle:**\n```bash\ntask 44 start  # Start with database schema\n[Design and implement schema]\ntask 44 done\n\ntask 45 start  # Next: authentication\n[Implement JWT auth]\ntask 45 done\n\n# Continue through dependency chain...\n```\n\n### Example 3: Debugging Investigation\n\n**User Request:** \"My Node.js app crashes with ECONNREFUSED\"\n\n**Task Decomposition:**\n```bash\ntask add \"Debug ECONNREFUSED error in Node.js app\" project:Debugging priority:H due:today +debugging +nodejs +urgent +investigation\n```\n\n**Lifecycle with Annotations:**\n```bash\ntask 50 start\ntask 50 annotate \"Error occurs during PostgreSQL connection\"\ntask 50 annotate \"Root cause: PostgreSQL service not running\"\ntask 50 annotate \"Solution: systemctl start postgresql\"\n[Provide debugging steps and code fixes]\ntask 50 done\n```\n\n### Example 4: Recurring Maintenance Task\n\n**User Request:** \"Create a script I need to run weekly to clean Docker images\"\n\n**Task Decomposition:**\n```bash\ntask add \"Weekly Docker cleanup script\" project:Maintenance recur:weekly due:friday priority:M +automation +docker +cleanup\n```\n\n**Lifecycle:**\n```bash\ntask 55 start\n[Write docker-cleanup.sh script]\ntask 55 done\n\n# Future instances auto-generate every Friday\ntask next  # Will show next week's instance\n```\n\n## Task Priority Guidelines\n\nUse this urgency matrix to assign priority:\n\n**priority:H (High) - Use when:**\n- Blocking other work\n- Production outage or critical bug\n- Security vulnerability\n- Hard deadline within 24-48 hours\n- Explicitly marked as urgent by user\n\n**priority:M (Medium) - Use when:**\n- Normal feature development\n- Non-blocking improvements\n- Deadline within 3-7 days\n- Standard maintenance work\n- Default for most tasks\n\n**priority:L (Low) - Use when:**\n- Nice-to-have enhancements\n- Documentation updates\n- Refactoring for cleanliness (not performance)\n- No specific deadline\n- Can be deferred without impact\n\n## Tag Taxonomy\n\n**Common Project Tags:**\n- `+feature` - New functionality\n- `+bugfix` - Fixing existing issues\n- `+refactor` - Code restructuring\n- `+testing` - Test creation\u002Fexecution\n- `+documentation` - Docs and comments\n- `+deployment` - Release and infrastructure\n- `+security` - Security-related work\n- `+performance` - Optimization work\n- `+debugging` - Investigation and diagnosis\n- `+maintenance` - Routine upkeep\n- `+automation` - Scripting and tooling\n- `+infrastructure` - DevOps and systems\n\n**Technology Tags:**\n- `+python`, `+javascript`, `+bash`, `+typescript`\n- `+docker`, `+kubernetes`, `+cicd`\n- `+postgresql`, `+redis`, `+mongodb`\n- `+fastapi`, `+react`, `+nextjs`\n\n**Status Tags:**\n- `+blocked` - Cannot proceed (annotate reason)\n- `+urgent` - Needs immediate attention\n- `+waiting` - Awaiting external input\n- `+review` - Ready for review\n\n## Handling Special Scenarios\n\n### Scenario 1: Mid-Task Scope Change\n\nIf requirements change while working:\n\n```bash\n# Modify existing task\ntask \u003CID> modify +new_tag description:\"Updated description\"\n\n# Or create dependent subtask for additional work\ntask add \"Additional scope: Email notifications\" depends:\u003CID> project:SameProject +feature\n```\n\n### Scenario 2: Blocked Work\n\nIf encountering blockers (missing credentials, API limits, permissions):\n\n```bash\n# Stop the task\ntask \u003CID> stop\n\n# Annotate the blocker\ntask \u003CID> annotate \"Blocked: Need AWS credentials from ops team\"\n\n# Mark as blocked\ntask \u003CID> modify +blocked\n\n# Explain to user what's needed to unblock\n```\n\n### Scenario 3: Multi-Session Work\n\nFor work spanning multiple conversations:\n\n**Session 1:**\n```bash\ntask add \"Build e-commerce platform - product catalog\" project:Ecommerce priority:H +feature\ntask 60 start\n[Implement product catalog]\ntask 60 done\n```\n\n**Session 2 (later):**\n```bash\n# Check existing project tasks\ntask project:Ecommerce status:pending\n\n# Create related task\ntask add \"Build e-commerce platform - shopping cart\" project:Ecommerce depends:60 priority:H +feature\ntask 61 start\n[Implement shopping cart]\ntask 61 done\n```\n\n### Scenario 4: Working with User's Existing Tasks\n\nIf user references an existing Taskwarrior task:\n\n**User:** \"Help me complete task 42: 'Optimize database queries'\"\n\n**Response:**\n```bash\n# Start user's existing task\ntask 42 start\n\n[Provide optimization recommendations and code]\n\n# Complete user's task\ntask 42 done\n\n# Show results\ntask 42 info\ntimew summary :ids\n```\n\n## Integration with Timewarrior\n\nTaskwarrior automatically integrates with Timewarrior when configured. Here's what happens:\n\n**When you start a task:**\n```bash\ntask \u003CID> start\n# Timewarrior begins tracking with tags from the task\n```\n\n**Check current tracking:**\n```bash\ntimew  # Shows what's currently being tracked\ntask active  # Shows active Taskwarrior tasks\n```\n\n**Stop tracking (when you stop or complete a task):**\n```bash\ntask \u003CID> stop  # Pauses tracking\ntask \u003CID> done  # Stops tracking and completes task\n```\n\n**View time reports:**\n```bash\ntimew summary :ids              # Total time per task\ntimew report :ids :week         # This week's breakdown\ntimew tags                      # Most-used tags\ntimew day                       # Today's time usage\n```\n\n## Workflow Enforcement Rules\n\n### MANDATORY RULES:\n\n1. **NO CODE BEFORE TASKS** - Always run `task add` BEFORE writing any code\n2. **ALWAYS START TASKS** - Run `task \u003CID> start` to activate time tracking\n3. **ALWAYS COMPLETE TASKS** - Run `task \u003CID> done` when work is delivered\n4. **USE PROPER ATTRIBUTES** - Every task needs project:, priority:, due:, and tags:\n5. **RESPECT DEPENDENCIES** - Work tasks in order defined by `depends:` relationships\n6. **ANNOTATE DECISIONS** - Use `task \u003CID> annotate` to document key choices\n7. **HANDLE BLOCKERS EXPLICITLY** - Stop tasks and mark as +blocked when stuck\n\n### VERIFICATION CHECKLIST:\n\nBefore delivering code, confirm:\n- ✅ Task was created with proper attributes\n- ✅ Task was started (appears in `task active`)\n- ✅ Time tracking is running (verify with `timew`)\n- ✅ Code is implemented and tested\n- ✅ Task is completed with `task done`\n- ✅ Time summary is shown\n\n## Refusing Non-Compliant Requests\n\nIf user asks for code without mentioning Taskwarrior, **proactively enforce the protocol**:\n\n**User:** \"Write me a Python script to parse CSV files\"\n\n**Your Response:**\n```\nBefore I write the code, I need to create a Taskwarrior task to track this work properly.\n\nI'll decompose this as:\ntask add \"Create CSV parser Python script\" project:DataProcessing priority:M due:today +python +scripting +parsing\n\nThen I'll start the task and implement the solution.\n\n[Proceed with task creation → task start → code implementation → task done]\n```\n\n## Success Metrics\n\nAfter completing work, provide these metrics:\n\n```bash\n# Task details\ntask \u003CID> info\n\n# Time spent\ntimew summary :ids\n\n# Project progress\ntask project:\u003CProjectName> completed\ntask project:\u003CProjectName> status:pending\n\n# Personal productivity\ntask completed count\ntask active count\n```\n\n## Quick Reference Commands\n\n| Operation | Command |\n|-----------|---------|\n| **Create task** | `task add \"description\" project:Name priority:M due:today +tag1 +tag2` |\n| **Start task** | `task \u003CID> start` |\n| **Stop task** | `task \u003CID> stop` |\n| **Complete task** | `task \u003CID> done` |\n| **View active tasks** | `task active` |\n| **View next tasks** | `task next` |\n| **Modify task** | `task \u003CID> modify priority:H +new_tag` |\n| **Annotate task** | `task \u003CID> annotate \"note\"` |\n| **View task details** | `task \u003CID> info` |\n| **List by project** | `task project:ProjectName list` |\n| **Show time tracking** | `timew` |\n| **Time summary** | `timew summary :ids` |\n| **Weekly report** | `timew report :ids :week` |\n\n## Expected User Workflow\n\n**Typical Interaction:**\n\n**User:** \"I need help with taskwarrior - create a FastAPI authentication system\"\n\n**Your Response:**\n```\nI'll enforce the Taskwarrior integration protocol for this work.\n\n## Phase 1: Task Decomposition\n\nCreating tasks for FastAPI authentication system:\n\ntask add \"Build FastAPI authentication system\" project:WebDev priority:H due:2days +fastapi +auth +security +backend\ntask add \"Implement JWT token generation\" project:WebDev depends:1 priority:H +jwt +auth\ntask add \"Create login\u002Flogout endpoints\" project:WebDev depends:2 priority:M +endpoints +api\ntask add \"Add password hashing with bcrypt\" project:WebDev depends:3 priority:M +security +passwords\ntask add \"Write authentication tests\" project:WebDev depends:4 priority:M +testing +pytest\n\n## Phase 2: Task Activation\n\ntask 1 start\ntimew  # Verify tracking started\n\n## Phase 3: Implementation\n\n[Now I'll implement the authentication system...]\n\n[Provide complete FastAPI auth code]\n\n## Phase 4: Completion\n\ntask 1 done\ntimew summary :ids\n\nTotal time: 45 minutes\nNext task: Implement JWT token generation (task 2)\n```\n\n## Best Practices\n\n### ✅ DO:\n- Create tasks for EVERY coding activity, no matter how small\n- Use descriptive task names that explain the \"what\" and \"why\"\n- Set realistic due dates based on complexity\n- Add multiple relevant tags for better filtering\n- Annotate tasks with important decisions or blockers\n- Leverage the dependency system for related work\n- Complete tasks when work is done (don't leave tasks hanging)\n- Review `task next` regularly to prioritize work\n\n### ❌ DON'T:\n- Skip task creation for \"quick\" tasks\n- Write code before creating and starting tasks\n- Use generic descriptions (\"Fix bug\" vs. \"Fix OAuth redirect loop\")\n- Ignore the dependency system\n- Leave tasks incomplete after delivering code\n- Forget to stop\u002Fcomplete tasks when switching contexts\n- Use priority:H for everything (dilutes urgency)\n\n## Troubleshooting\n\n### Issue: \"Task not tracking time\"\n\n**Solution:**\n```bash\n# Verify Timewarrior is installed\nwhich timew\n\n# Check if task is active\ntask active\n\n# Manually start tracking if needed\ntimew start +tag1 +tag2\n```\n\n### Issue: \"Can't find task ID\"\n\n**Solution:**\n```bash\n# List all tasks\ntask list\n\n# Show task details by description search\ntask \u002Fkeyword\u002F list\n\n# Show recently completed tasks\ntask completed\n```\n\n### Issue: \"Forgot to start task before coding\"\n\n**Solution:**\n```bash\n# Start the task now (retroactively)\ntask \u003CID> start\n\n# Manually adjust Timewarrior if needed\ntimew track yesterday 2:00pm - 3:30pm +projecttag +featuretag\n```\n\n## Integration with Your Workflow\n\nThis skill integrates seamlessly with:\n- **VS Code Taskwarrior extensions** - See tasks in your editor sidebar\n- **CI\u002FCD pipelines** - Auto-create tasks for deployments\n- **Git workflows** - Reference task IDs in commit messages\n- **Team collaboration** - Shared Taskwarrior server for team visibility\n- **Reporting tools** - Export to JSON for dashboards\n\n## Summary\n\nThis skill enforces a **mandatory, comprehensive Taskwarrior integration** for ALL coding activities. It ensures:\n\n✅ Every piece of work is tracked as a task\n✅ Time spent is automatically accounted via Timewarrior\n✅ Complex projects are decomposed into manageable, linked subtasks\n✅ Complete audit trail of all work performed\n✅ Proper prioritization and deadline management\n✅ Full lifecycle from creation → activation → implementation → completion\n\n**NO CODE GETS WRITTEN without following the complete Taskwarrior protocol.**\n",{"name":5,"description":7},"master","be156301b65e301887f327d08190ed4f17ba08d2","docs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fproductivity\u002F001-jeremy-taskwarrior-integration\u002Fskills\u002F001-jeremy-taskwarrior-integration",0,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp","https:\u002F\u002Fgithub.com\u002Fsandraschi","2026-11-13 15:00:21",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add sandraschi\u002Fdocumentation-mcp --skill 001-jeremy-taskwarrior-integration",{"tool":62,"command":63},"bunx","bunx skills add sandraschi\u002Fdocumentation-mcp --skill 001-jeremy-taskwarrior-integration",{"tool":65,"command":66},"pnpm","pnpm dlx skills add sandraschi\u002Fdocumentation-mcp --skill 001-jeremy-taskwarrior-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fproductivity\u002F001-jeremy-taskwarrior-integration\u002Fskills\u002F001-jeremy-taskwarrior-integration\u002FSKILL.md",true,[],[71,94,121,131,156,182],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":81,"publishedAt":44},"01M6PFAWAHEJJCKKVNXEWNK87W","Docs Research","Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fsrc\u002Fdocs_mcp\u002Fskills\u002Fdocs-research\u002FSKILL.md",[77,80],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[82,83,84,85,86,87,88,89,90,91,92,93],"docs research","docs","research","standards","use","packaging","ask","server","search","fastmcp","documentation","MCP",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":44},"01M6PFAN4DAENMY574Q7Q3CB3H","wrappee-drift","Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API\u002Fdocs, not training-data memory) and against comparable\u002Fcompeting wrappers. Trigger when the user says \"wrappee drift\" followed by a repo name, \"capability audit\" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth\u002Farchive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's\u002Fcompetitors' actual current capabilities.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwrappee-drift\u002FSKILL.md",[],[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"drift","wrappee drift","api","data","audit","capabilities","training","memory","features","repo audit","competitors","fleet","now","software","tool list","only","never","coverage","list","read",{"skillNo":122,"name":123,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":130,"publishedAt":44},"01M6PFADA3X031SK3W3T6X0N6H","modules","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002Fmodules\u002FSKILL.md",[126,129],{"categoryNo":127,"categoryName":128,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[123],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":141,"publishedAt":44},"01M6PFA8YA029N68TW0X31FB1W","mcp-standards","Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI\u002FCD workflows.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002FSKILL.md",[137,140],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[142,93,85,86,143,144,145,146,147,148,29,149,150,151,152,153,92,154,155,87],"mcp standards","monitoring","sampling","scaffolding","servers","cd","error","CI\u002FCD","access","ci","mcp servers","error handling","workflows","testing",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":164,"publishedAt":44},"01M6PFA1XX344WX57B0DJZY94Q","webapp-cua-test","Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR \"Connected\" wait, sidebar nav walk) for a fleet MCP server repo under D:\\Dev\\repos. Trigger when the user says \"cua webapp test\" or \"webapp clickthrough\" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill \u002F cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwebapp-cua-test\u002FSKILL.md",[162,163],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[165,166,167,168,169,93,170,171,172,29,173,174,175,176,177,178,179,180,89,181],"webapp","test","webapp cua test","playwright","mcp server","dev","dom","assertions","trigger","click","app","tauri","repo","stack","e2e","ocr","browser",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":44},"01M6PF9WYF6NWJR7WVN38TT0WH","ship","Final release gate for a fleet MCP server repo under D:\\Dev\\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says \"ship it\", \"ship\" followed by a repo name, \"release\" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix\u002Fnsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fship\u002FSKILL.md",[188],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[184,177,29,173,190,191,192,35,193,39,194,89,195,170,196,197,198,169,199,93],"gates","ship it","artifact","say","publish","push","shipping","quality gates","commit","github"]