skills.rest
is-ivanov
is-ivanovCOMMUNITY
Explore all skills by this author →
GitHub

task

Create numbered bug or refactoring tasks with spec.md and progress.md files.

2|1|Updated Nov 7, 2025
Search Tags:#workflow automation#refactoring#specification#progress tracking#bug tracking#task creation
One-click install
npx skills add https://github.com/is-ivanov/rpm-ddd --skill task-is-ivanov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/is-ivanov/rpm-ddd/tree/main/.opencode/skills/task
Command: npx skills add https://github.com/is-ivanov/rpm-ddd --skill task-is-ivanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how new bugs and refactoring tasks are created so teams do not lose time deciding naming, numbering, documentation structure, or progress tracking format.

Core Features & Use Cases

  • Global task numbering: Finds the next available task number across both active and completed task folders, with verification to avoid collisions.
  • Structured task creation: Creates a task folder, gathers the right details interactively, and generates both spec.md and progress.md from repository templates.
  • Workflow-aware planning: Adapts progress tracking to backend, frontend, mixed, or refactoring work so execution steps match the implementation scope.
  • Use Case: When a team member discovers a UI bug or plans a backend cleanup, they can use this Skill to create a properly numbered task package with a clear specification and actionable checklist.

Quick Start

Ask the AI to create a new bug or refactoring task with a short title and it will guide you through the required details and generate the tracking files.

Frequently Asked Questions about task

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

FAQPage Schema
How do I create a standardized bug tracking task with progress tracking files?▼

Standardized bug tracking tasks are created by interactively gathering details and generating a numbered task folder with spec.md and progress.md files from repository templates. This ensures consistent documentation structure and progress tracking format.

How does global sequential task numbering work for repository workflows?▼

Global sequential task numbering scans active and completed task directories to find the next available number, performing folder collision checks to verify uniqueness before creating the new task package.

Can I generate separate progress plans for backend and frontend refactoring tasks?▼

Yes, tailored progress plans are generated for backend, frontend, mixed, or refactoring work. The Skill adapts progress tracking checklists so execution steps match the specific implementation scope of the task.

What is the best way to standardize refactoring task specifications across a team?▼

Standardizing refactoring task specifications is achieved by using template-based spec generation within numbered task directories, ensuring all team members follow the same documentation structure and naming conventions.

Do I need existing repository templates to use automated task creation?▼

Existing repository templates are required because this Skill generates spec.md and progress.md files directly from them, relying on these templates to populate the standardized implementation scope and tracking format.

Related Skills

Explore More Product & Management Skills→
paycruxpaycrux

finalize

Merge Implementation Map into spec.md and remove temporary task documents.

Official
Advanced
OreStudioOreStudio
25

new-sprint-skill

Update sprint backlog files, version strings, and CI configuration for a new Agile sprint.

Official
Intermediate
claude-office-skillsclaude-office-skills
368

ClickUp Automation

Automates ClickUp tasks, workflows, time tracking, and goals via predefined MCP tools.

Official
Advanced
NVIDIA-NeMoNVIDIA-NeMo
58

nmp-cli

Manage NeMo Platform CLI command registration and SDK-based generation.

Official
Advanced