dev-tasks

Organize dev notes into ideas, issues, and decisions with collision checks.

118|12|Updated May 5, 2026
One-click install
npx skills add https://github.com/alecs5am/ralphy --skill dev-tasks-alecs5am
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-tasks
Source: https://github.com/alecs5am/ralphy/tree/main/.agents/skills/dev-tasks
Command: npx skills add https://github.com/alecs5am/ralphy --skill dev-tasks-alecs5am

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes Ralphy's dev notes inbox to ensure ideas, issues, and decisions are captured, deduplicated, and properly categorized.

Core Features & Use Cases

  • Capture and classify thoughts into ideas, issues, or decisions.
  • Perform cross-inbox collision checks before filing new items and route updates to existing ones.
  • Sync between notes/ideas, notes/issues, and notes/decisions with the dev-issues / dev-loop workflows.

Quick Start

Capture a thought as an idea or note using the dev-tasks flow.

Frequently Asked Questions about dev-tasks

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

FAQPage Schema
How do I capture and organize dev notes so ideas and issues don't get duplicated?

To capture dev notes without duplication, this Skill performs cross-inbox collision checks before filing new items, routing updates to existing records and classifying them into structured ideas, issues, or decisions categories.

What is the best way to categorize developer decisions and issues in a structured inbox?

Categorizing developer decisions and issues is handled by enforcing a structured inbox format with monotonic numbering, separating records into notes/ideas, notes/issues, and notes/decisions directories.

Can I promote mature dev notes into a backlog after capturing them?

Yes, you can promote mature dev notes into the backlog. The workflow coordinates with dev-issues and dev-loop to sync categorized ideas and decisions from the inbox into downstream development processes.

How does collision checking work when logging new development ideas?

Collision checking scans the existing dev notes inbox for similar ideas, issues, or decisions before creating a new file. If a match is found, the update is routed to the existing item to prevent duplication.

Do I need a specific workflow setup to use dev-tasks for issue tracking?

You need an interactive session setup that adheres to the dev-tasks workflow structure, utilizing the notes/ideas, notes/issues, and notes/decisions directories to properly log items and coordinate with dev-issues and dev-loop.