research-and-align

Researches existing solutions and aligns on key decisions before consequential implementation.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill research-and-align-pikachu0310
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-and-align
Source: https://github.com/pikachu0310/codex-agent-ops-public/tree/main/.agents/skills/research-and-align
Command: npx skills add https://github.com/pikachu0310/codex-agent-ops-public --skill research-and-align-pikachu0310

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Ambiguous or high-impact requests often lead to rework when implementation starts before the approach is agreed upon. This Skill prevents wasted effort by investigating the current environment and existing solutions first, then confirming only the decisions that materially change the outcome with the user before writing code. ## Core Features & Use Cases - Gate Detection: Determines whether a request warrants full research-and-alignment (architecture changes, new features, UI/UX direction, migrations, destructive actions) or just a quick check for small fixes and approved plans. - Prior-Art Research: Inspects repository instructions, code, dependencies, past tasks, and official documentation, searching for existing solutions in order: in-repo implementations, standard features, maintained libraries, and public examples. - Lightweight Alignment: Presents one recommended approach with key trade-offs, asks at most three outcome-changing questions with suggested answers, and proceeds on reasonable assumptions for everything else. - Use Case: Before adding a new dependency or redesigning a data model, use this Skill to survey existing libraries, compare adopt-versus-build options, and confirm the direction with the requester in the same task. ## Quick Start Ask the agent to research existing solutions and align on the approach before implementing the requested feature or architectural change.

Frequently Asked Questions about research-and-align

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

FAQPage Schema
How do I research existing solutions before writing new code?

Search in order: existing in-repo implementations, standard platform features, official library capabilities, maintained third-party libraries, then public examples. Compare only the differences that affect the decision, prefer primary sources, and conclude whether to adopt, adapt, combine, or build new.

When should I align with the requester before implementing?

Align first when requirements have multiple valid interpretations, when changing architecture, dependencies, data models, or UI/UX direction, or when the work involves migrations, deletions, or publishing. Skip the full process for explicit small fixes or already-approved plans.

How many clarifying questions should I ask before starting a task?

Ask at most three questions, ideally just one, and only about points that change the outcome. Attach a recommended answer to each question, and proceed with stated reasonable assumptions for choices that do not affect the result.

When should I not use a research-and-alignment workflow?

Skip it for concrete small fixes, clear diagnostics, or execution of a plan the user already approved. In those cases a brief check of the current state is enough, and full research would only add ceremony and delay.

Does this workflow create design documents or commits automatically?

No. Design documents, plans, context files, and commits are not created automatically. They are produced only when the deliverable requires them or the user explicitly requests them.