One-click install
npx skills add https://github.com/lciacci/tessera --skill framework-evaluation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: framework-evaluation
Source: https://github.com/lciacci/tessera/tree/main/skills/framework-evaluation
Command: npx skills add https://github.com/lciacci/tessera --skill framework-evaluation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents ad-hoc decisions about external tools, frameworks, libraries, and patterns by providing a repeatable evaluation process grounded in Tessera's design principles.

Core Features & Use Cases

  • Structured Evaluation: Assess identity, maturity, problem-space overlap, integration cost, implementation fit, lock-in, and maintenance risk.
  • Decision Documentation: Produce a complete Architecture Decision Record with adoption verdict, concepts to retain, rejected alternatives, and re-evaluation triggers.
  • Use Case: When a new agentic coding framework appears, evaluate whether Tessera should adopt it fully, borrow selected patterns, run it alongside Tessera, continue independently, or reject it.

Quick Start

Use the framework-evaluation skill to assess whether the specified external tool or framework should be adopted by Tessera and produce the corresponding ADR.

Frequently Asked Questions about framework-evaluation

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

FAQPage Schema
How do I evaluate whether to adopt a new software framework?

Framework evaluation requires evidence-based analysis across maturity, problem-space overlap, integration cost, pattern fit, lock-in, and maintenance risk. This process prevents ad-hoc adoption decisions by grounding the assessment in structured design principles.

What is an architecture decision record for framework selection?

An architecture decision record (ADR) for framework selection documents the adoption verdict, concepts to retain, rejected alternatives, and explicit re-evaluation triggers. It provides a repeatable, defensible record of the technology assessment process and its outcomes.

When should I re-evaluate an existing framework adoption decision?

You should re-evaluate a framework adoption decision when explicit re-evaluation triggers occur. The evaluation process requires defining these triggers in the architecture decision record to ensure ongoing technology assessments remain defensible.

How do I document lock-in risk and integration cost for a technology assessment?

To document lock-in risk and integration cost for a technology assessment, analyze the external tool against your system's design principles. Record the findings in an architecture decision record alongside the adoption verdict and maintenance risk analysis.

Can I borrow patterns from a framework without fully adopting it?

Yes, you can borrow selected patterns without full adoption. The evaluation process determines whether to adopt a framework fully, borrow specific patterns, run it alongside existing systems, continue independently, or reject it.

What are the limitations of ad-hoc framework selection?

Ad-hoc framework selection lacks a repeatable evaluation process, leading to undefensible adoption decisions. It skips evidence-based analysis of maturity, overlap, integration cost, lock-in, and maintenance risk, missing critical architecture decision record documentation.