ra-methodology

Enforce Response Awareness methodology with complexity scoring and assumption tagging.

Updated Sep 8, 2025
One-click install
npx skills add https://github.com/dtannen/pm --skill ra-methodology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ra-methodology
Source: https://github.com/dtannen/pm/tree/main/.claude-plugin/skills/ra-methodology
Command: npx skills add https://github.com/dtannen/pm --skill ra-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures adherence to the Response Awareness (RA) methodology, promoting thoroughness in task management, complexity assessment, and assumption tracking throughout the development lifecycle.

Core Features & Use Cases

  • Task Creation & Management: Guides the creation of tasks with mandatory complexity scoring and RA mode setting.
  • Complexity Assessment: Provides a 1-10 scale for scoring task complexity, influencing the level of RA rigor required.
  • RA Tagging: Facilitates the critical practice of tagging assumptions and decisions during implementation using the add_ra_tag MCP tool.
  • Knowledge Capture: Standardizes the process for documenting insights, gotchas, and solutions encountered during development.
  • Workflow Enforcement: Mandates specific task status transitions (TODO → IN_PROGRESS → REVIEW → DONE) to ensure proper validation of assumptions.
  • Use Case: When creating a new feature, use this skill to ensure the task is properly scoped, its complexity is assessed, all assumptions made during implementation are tagged, and the task goes through a review process before completion.

Quick Start

Use the ra-methodology skill to create a new task for implementing user authentication with a complexity score of 7.

Frequently Asked Questions about ra-methodology

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

FAQPage Schema
What is Response Awareness methodology in AI-assisted development?

Response Awareness methodology standardizes AI-assisted development by enforcing complexity scoring, assumption tracking, and structured task workflows. It mandates tasks move through TODO, IN_PROGRESS, REVIEW, and DONE statuses to validate assumptions before completion.

How do I track assumptions made by AI agents during software development?

To track assumptions during software development, use the RA tagging practice to explicitly tag decisions and assumptions during implementation. This is facilitated by the add_ra_tag MCP tool, ensuring critical assumptions are documented and validated through a structured review process.

How do I assess task complexity for AI-assisted development workflows?

Assess task complexity using a 1-10 scoring scale to determine the level of rigor required. High-complexity tasks trigger RA-Light or RA-Full modes, mandating multi-agent orchestration and verification phases to manage the development workflow effectively.

Can I use RA methodology for simple tasks or is it only for complex features?

RA methodology accommodates varying task complexities through a 1-10 scoring scale. Lower scores require standard task management, while higher complexity scores trigger RA-Light or RA-Full modes, mandating multi-agent orchestration and verification phases.

What is the best way to manage task status transitions in AI development workflows?

The best way to manage task status transitions is enforcing a strict TODO to IN_PROGRESS to REVIEW to DONE workflow. This standardizes validation of assumptions and ensures proper documentation of insights, gotchas, and solutions encountered during implementation.

When should I use RA-Full mode instead of RA-Light mode for task management?

Use RA-Full mode for high-complexity tasks requiring rigorous multi-agent orchestration and verification phases. RA-Light mode offers a less stringent workflow for high-complexity tasks, while both modes enforce explicit assumption tagging and complexity scoring.