Back to Skills

pact-prepare-research

verified

Research methodologies and documentation gathering workflows for PACT Prepare phase. Use when: conducting technology research, evaluating API documentation, comparing framework options, analyzing library choices, gathering requirements, or creating technology comparison matrices. Triggers on: research, requirements gathering, API exploration, documentation review, technology evaluation, library comparison, prepare phase.

View on GitHub

Marketplace

pact-marketplace

ProfSynapse/PACT-prompt

Plugin

PACT

development

Repository

ProfSynapse/PACT-prompt
37stars

pact-plugin/skills/pact-prepare-research/SKILL.md

Last Verified

January 25, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/ProfSynapse/PACT-prompt/blob/main/pact-plugin/skills/pact-prepare-research/SKILL.md -a claude-code --skill pact-prepare-research

Installation paths:

Claude
.claude/skills/pact-prepare-research/
Powered by add-skill CLI

Instructions

# PACT Prepare Research Methodology

Structured approaches for the Prepare phase of PACT. This skill provides
frameworks for systematic research, documentation gathering, and technology
evaluation to build a solid foundation before architecture and implementation.

## Research Workflow

### Phase 1: Define Research Scope

Before starting research, clearly define:

```markdown
## Research Scope Definition

### Primary Question
What specific problem are we trying to solve?

### Success Criteria
What would make a solution acceptable?
- [ ] Performance requirements
- [ ] Integration requirements
- [ ] Security requirements
- [ ] Budget constraints

### Constraints
What limitations must we work within?
- Technology stack restrictions
- Team expertise
- Timeline
- Licensing requirements
```

### Phase 2: Source Prioritization

Prioritize sources by authority and reliability:

| Priority | Source Type | Examples | Trust Level |
|----------|-------------|----------|-------------|
| 1 | Official documentation | Docs, API references | Highest |
| 2 | Official repositories | GitHub READMEs, wikis | Very High |
| 3 | Maintainer content | Blog posts by core team | High |
| 4 | Community verified | Stack Overflow accepted answers | Medium |
| 5 | Third-party tutorials | Blog posts, videos | Low-Medium |
| 6 | AI-generated content | ChatGPT, Copilot | Verify Required |

**Source Verification Checklist:**
- [ ] Publication date within 12 months (for version-specific info)
- [ ] Author has verifiable credentials
- [ ] Information matches official docs
- [ ] Code examples actually work

### Phase 3: Documentation Types to Gather

Collect these documentation types for complete understanding:

**1. API References**
```markdown
## API Documentation Checklist
- [ ] Authentication methods
- [ ] Rate limits and quotas
- [ ] Available endpoints
- [ ] Request/response formats
- [ ] Error codes and handling
- [ ] SDK availability
- [ ] Webhook support
```

**2. Configuration Guides**
```markd

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
7855 chars