research

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

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/vanderleik/greenfiend-project --skill research-vanderleik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/vanderleik/greenfiend-project/tree/main/.github/skills/research
Command: npx skills add https://github.com/vanderleik/greenfiend-project --skill research-vanderleik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This YAML Skill enables teams to generate a structured decisions document for a project phase, capturing the decisions to be made, the available alternatives with trade-offs, and a recommended path. It uses the general project plan, canonical decisions, and planned phases as reference points to ensure alignment with the overall strategy.

Core Features & Use Cases

  • Identify required technical decisions for a phase by examining the project plan and phase capabilities.
  • Compare multiple implementation options (libraries, frameworks, services) and surface trade-offs, constraints, and risks.
  • Produce a structured decisions document that feeds into the plan-phase skill and records decisions for traceability.

Quick Start

Provide the phase context and capabilities, and let this skill generate a structured decisions document with options, trade-offs, and a recommended path.

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 for a project phase?

To structure technical decisions for a project phase, you identify the required decisions and generate a document listing available implementation options, trade-offs, and a recommended path aligned with the project plan.

What is the best way to compare architecture options and surface trade-offs?

Comparing architecture options is done by examining planned phase capabilities to evaluate multiple libraries, frameworks, and services, which surfaces distinct trade-offs, constraints, and risks for each implementation path.

When do I need to generate a decisions document for phase planning?

You need a decisions document for phase planning when multiple implementation options exist for the technology stack, requiring a structured comparison of alternatives to ensure alignment with canonical decisions and overall strategy.

How do I ensure my technical decisions align with the overall project plan?

To ensure technical decisions align with the project plan, you use the general project plan, canonical decisions, and planned phases as reference points to guide the selection of a recommended implementation path.

Can I use this approach to analyze any framework or library for my stack?

Yes, you can analyze any framework, library, or service for your stack by applying this structured research process to surface constraints and trade-offs whenever multiple implementation options exist for that specific technology.