skills.rest
matteocervelli
matteocervelliCOMMUNITY
Explore all skills by this author →
Website𝕏@matteocervelliGitHub

technical-annotator

Annotate user stories with tech stacks, effort estimates, and risk assessments.

25|2|Updated Oct 26, 2025
Search Tags:#architecture#implementation#estimation#risk#user-stories#tech-annotation
One-click install
npx skills add https://github.com/matteocervelli/llms --skill technical-annotator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-annotator
Source: https://github.com/matteocervelli/llms/tree/main/user-story-system/.claude/skills/technical-annotator
Command: npx skills add https://github.com/matteocervelli/llms --skill technical-annotator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adds technical context, implementation hints, and effort estimates to user stories to accelerate engineering planning.

Core Features & Use Cases

  • Identify tech stack and components
  • Provide concrete implementation hints
  • Estimate effort and assess risk
  • Support technical decision making for backlog items

Quick Start

Annotate US-0005 with recommended stack and effort estimates, or query for tech requirements for US-0012.

Frequently Asked Questions about technical-annotator

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

FAQPage Schema
How do I add technical context and effort estimates to user stories?▼

Technical annotation enriches user stories with implementation details, recommended tech stacks, effort estimates, and risk assessments. Apply the annotator to backlog items to surface technology requirements, component dependencies, and concrete implementation hints that accelerate engineering planning.

What information does technical annotation provide for a user story?▼

Technical annotation identifies data needs, UI/API components, affected system parts, and technology recommendations. It returns structured notes including implementation hints, effort estimates, risk assessments, and tech stack guidance to support technical decision-making.

Can I use technical annotation to estimate implementation effort for backlog items?▼

Yes. The annotator analyzes user story requirements and returns effort estimates alongside risk assessments and tech stack recommendations, enabling teams to prioritize backlog items and plan sprints with better visibility into engineering complexity.

How does technical annotation identify required components and dependencies?▼

The annotator examines story data to surface UI/API components, data dependencies, and affected system parts. It maps these to technology recommendations and implementation hints, creating a complete technical picture for each user story.

When should I use technical annotation in the development workflow?▼

Apply technical annotation early during backlog refinement and story intake to embed implementation context before estimation and sprint planning. This accelerates technical decision-making and reduces estimation uncertainty.

Related Skills

Explore More Software Engineering Skills→
Eric-Pacheco95Eric-Pacheco95

acceptance-criteria

Convert user stories into Given-When-Then acceptance criteria in Gherkin format or checklist.

Community
Intermediate
b566776b566776

bmad-correct-course

Analyze sprint change impacts across PRD, epics, architecture, and UX documents.

Community
Advanced
truongnattruongnat

senior-architect

Generate C4, sequence, and ERD diagrams for software system architecture.

Community
Advanced
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

Break down epics into user stories with acceptance criteria and sprint groupings.

Community
Advanced