skills.rest
devfullcycle
devfullcycleOFFICIAL
Explore all skills by this author →
WebsiteGitHub

research

Generate a structured decisions document comparing technical options for a project phase.

16|145|Updated Mar 16, 2026
Search Tags:#architecture#research#trade-offs#options#phase-planning#technical-decisions
One-click install
npx skills add https://github.com/devfullcycle/mba-ia-greenfield-project --skill research-devfullcycle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/devfullcycle/mba-ia-greenfield-project/tree/main/.claude/skills/research
Command: npx skills add https://github.com/devfullcycle/mba-ia-greenfield-project --skill research-devfullcycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Research technical options and generate a structured decisions document for a project phase. This document sits between the general plan and the implementation plan — it identifies decisions that need to be made, presents alternatives with trade-offs, and recommends a path. The user reviews, decides, and the result feeds the plan-phase skill.

Core Features & Use Cases

  • Identify and compare technical options for a given project phase (e.g., frameworks, libraries, architectural patterns).
  • Produce a canonical decisions document outlining alternatives, trade-offs, constraints, and recommended paths for the plan-phase.
  • Reuse canonical decisions from docs/decisions to ensure consistency and avoid re-arguing settled choices.

Quick Start

Review the current phase plan and generate a structured decisions document.

Frequently Asked Questions about research

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

FAQPage Schema
How do I structure technical decisions from architecture research for a project phase?▼

Generate a structured technical decisions document by identifying viable implementation options for a project phase, presenting alternatives with trade-offs, and recommending a path that aligns with the project plan.

What is a technical decisions document and when do I need one for architecture planning?▼

A technical decisions document sits between the general plan and implementation plan, capturing architecture trade-offs and recommended paths. You need one when a project phase has multiple viable implementations requiring a settled technical decision.

How do I compare technical options like frameworks and architectural patterns with trade-offs?▼

Compare technical options by identifying alternatives for a project phase, documenting constraints, and producing a structured decisions document that presents architecture trade-offs and a recommended path to feed the plan-phase workflow.

Can I reuse canonical technical decisions to avoid re-arguing settled architecture choices?▼

Yes, you can reuse canonical technical decisions from docs/decisions to ensure consistency and avoid re-arguing settled architecture choices, applying them directly to new project phase planning and trade-off analysis.

Does the technical decisions document integrate with the plan-phase workflow?▼

Yes, the technical decisions document aligns with the project plan and feeds directly into the plan-phase workflow, ensuring architecture options and recommended paths are reviewed before implementation planning begins.

Related Skills

Explore More Software Engineering Skills→
proyecto26proyecto26
42

requirements-scoping

Structure ambiguous system design prompts into functional requirements, non-functional constraints, and out-of-scope boundaries.

Official
Intermediate
vanderleikvanderleik

research

Generate a structured decisions document listing options, trade-offs, and a recommended path.

Community
Advanced
devfullcycledevfullcycle
16

plan-phase

Generate technical implementation plans with steps, dependencies, tests, and acceptance criteria.

Official
Advanced
cy-walicy-wali

architecture

Generate Architecture Decision Records documenting technology decisions with trade-offs.

Community
Advanced