Technical Research & Architecture

Document technical architecture, technology choices, and risk assessments in a Tech.md file.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rghsoftware/context-engine --skill technical-research-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Technical Research & Architecture
Source: https://github.com/rghsoftware/context-engine/tree/main/context-engine/skills/plan-research
Command: npx skills add https://github.com/rghsoftware/context-engine --skill technical-research-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of translating a feature specification into a concrete technical plan, ensuring that architecture decisions, technology choices, and risk assessments are thoroughly considered before implementation begins.

Core Features & Use Cases

  • Architecture Planning: Defines the high-level system design for a new feature.
  • Technology Selection: Recommends appropriate technologies and patterns based on project context.
  • Risk Assessment: Identifies potential technical challenges and proposes mitigation strategies.
  • Use Case: After a feature specification is approved, use this Skill to generate a Tech.md document outlining the proposed architecture, key technical decisions, and stack-specific implementation details.

Quick Start

Use the plan research skill to research how to build the feature described in Context/Features/NNN-FeatureName/Spec.md.

Frequently Asked Questions about Technical Research & Architecture

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

FAQPage Schema
How do I plan technical architecture for a new software feature?

Technology selection for feature development involves analyzing project context, existing architecture decision records, and active rules to recommend appropriate technologies and patterns that align with your current system design before implementation begins.

When do I need to generate a technical architecture document?

You need to generate a technical architecture document during the planning phase immediately after a feature specification is approved, ensuring all architecture decisions and risk assessments are thoroughly considered before code implementation begins.

What is included in a technical risk assessment for feature development?

A technical risk assessment for feature development identifies potential technical challenges and proposes mitigation strategies, documenting these alongside high-level system design and stack-specific implementation details within a Tech.md file.

Does architecture planning require an approved feature specification?

Yes, architecture planning requires an approved feature specification as input, along with project CLAUDE.md files, existing ADRs, and active .claude/rules files to ensure the technical plan aligns with established project constraints.

Best way to document technology choices before implementation?

The best way to document technology choices before implementation is to generate a structured Tech.md file that records the proposed architecture, key technical decisions, and stack-specific implementation details based on thorough research of feature specifications.