ada-research-planning

Stress-test plans, build domain models, and decompose large work into specs and tickets.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-research-planning-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-research-planning
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-research-planning
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-research-planning-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning vague ideas into executable plans often fails because assumptions go untested, terminology stays ambiguous, and large tasks exceed what a single agent session can handle. This Skill provides structured workflows for pressure-testing plans, modeling domains, and decomposing work into verifiable specs and tickets. ## Core Features & Use Cases - Grilling and Wayfinder Planning: Run focused interviews that expose failure modes and unstated assumptions, then build decision maps with blocking dependencies for work too large for one session. - To-Spec and To-Tickets Decomposition: Synthesize conversations into specifications preserving decisions, constraints, and open questions, then break them into tracer-bullet tickets with scope, acceptance criteria, and expected files. - Strategic Reading and Skill Self-Evolution: Analyze books or articles against a strategic question with Do/Avoid/Watch-for outputs, and audit agent skills across six dimensions including process design, example quality, and cross-file consistency. - Use Case: Before starting a multi-week migration, use grilling to surface at least three failure modes, build a domain model with unambiguous shared terminology, then decompose the work into tickets each declaring blockers, scope, and acceptance checks. ## Quick Start Ask the agent to grill your current project plan and then decompose it into a decision map with tickets.

Frequently Asked Questions about ada-research-planning

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

FAQPage Schema
How do I break down a large project into manageable tickets?

Use the Wayfinder workflow: first generate a decision map listing all decisions and their dependencies, then resolve them ticket by ticket. Each ticket should declare blocking prerequisites, scope boundaries, acceptance criteria, and expected output files.

How to stress-test a plan before implementation?

Run a grilling session: a focused interview probing goals, constraints, stakeholders, failure modes, trade-offs, and irreversible decisions. Continue until at least three failure modes or unstated assumptions are exposed before finalizing the plan.

What is domain modeling in software planning?

Domain modeling establishes a ubiquitous language, then identifies entities, value objects, workflows, invariants, and boundaries. The key principle is that every term must be usable unambiguously by the team, since vague terminology is more dangerous than none.

When should I stop iterating on skill or document improvements?

Stop when a full audit round produces no substantive improvements, typically after two consecutive unproductive rounds. Documentation does not need continuous refactoring like code, so avoid turning self-evolution into refactoring addiction.

What are the limitations of strategic book analysis?

Strategic reading requires a clear strategic question upfront and outputs Do, Avoid, and Watch-for recommendations rather than generic summaries. The Book Mirror method fails when it becomes mere summarization instead of mapping source ideas to the reader's context.