task

Create structured markdown task files for bugs, refactoring, and QA.

45|13|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/rakovi4/continue-framework --skill task-rakovi4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/rakovi4/continue-framework/tree/main/.claude/skills/task
Command: npx skills add https://github.com/rakovi4/continue-framework --skill task-rakovi4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of managing tasks with spec and progress tracking, especially useful for organizing and documenting tasks like bugs, refactoring, or QA work.

Core Features & Use Cases

  • Task Creation: Automates the creation of structured tasks with a specified type (bug, refactoring, or QA).
  • Progress Tracking: Facilitates tracking the progress of a task through various stages such as discovery, design, and implementation.
  • Automated Workflow: Generates spec and progress markdown files, ensuring tasks are well-documented and easy to follow.
  • Use Case: Perfect for project managers and developers looking to maintain a structured approach to task management, especially when dealing with bug fixes, code refactoring, or QA checks.

Quick Start

Create a new task for bug fixing with the /task bug "Find memory leak" command.

Frequently Asked Questions about task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create structured markdown files for software bug tracking and task management?

To create structured markdown files for bug tracking, you provide a task type and title to generate spec and progress documentation. This automated task creation ensures software development workflows remain organized without manual file setup.

Can I track progress through discovery, design, and implementation stages for code refactoring tasks?

Yes, you can track progress through discovery, design, and implementation stages for code refactoring tasks. The generated progress markdown files facilitate tracking work across these various stages to maintain clear documentation throughout the lifecycle.

What is the best way to document QA checks and software development tasks automatically?

The best way to document QA checks and software development tasks automatically is by specifying a task type like QA to generate structured spec files. This ensures tasks are well-documented and easy to follow for project managers and developers.

Does this task management approach require specific user input to generate spec and progress files?

Yes, this task management approach requires user input to create a new task with a specified type and title. Providing the task category, such as bug or refactoring, and a descriptive title is necessary to trigger the automated markdown file generation.

How do I start a new task for bug fixing using a structured markdown workflow?

You start a new bug fixing task by executing the creation command with the bug type and a title, such as specifying a memory leak. This initializes the spec and progress markdown files needed to document the resolution workflow.