torre-context

Aggregate TORRE architecture, sprint status, bugs, file map, and conventions into markdown context.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/lfggarcia/dnd-app --skill torre-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: torre-context
Source: https://github.com/lfggarcia/dnd-app/tree/main/.github/skills/torre-context
Command: npx skills add https://github.com/lfggarcia/dnd-app --skill torre-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a concise, up-to-date context for TORRE development tasks, enabling teammates to quickly align on architecture, sprint status, and conventions.

Core Features & Use Cases

  • Auto-loads project architecture, game design references, sprint status, bug list, file map, and coding conventions for quick reference.
  • Used during feature planning, debugging, onboarding, and sprint reviews to align teams on design decisions and project structure.
  • Useful for onboarding new contributors and validating decisions against the current project plan.

Quick Start

Review this context before starting TORRE work to align on architecture and sprint goals.

Frequently Asked Questions about torre-context

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

FAQPage Schema
How do I provide full project context for a React Native team during onboarding?

Providing full project context for a React Native team involves aggregating architecture, sprint status, known bugs, file maps, and conventions into a single reference. This aligns teammates on design decisions and project structure during onboarding.

What is the best way to align developers on sprint planning and project architecture?

Aligning developers on sprint planning and project architecture requires a centralized context document that loads operational guidance. This ensures teams validate decisions against the current project plan and design references quickly.

How does loading markdown context help with debugging and feature work?

Loading markdown context helps with debugging and feature work by auto-loading project architecture, bug lists, and coding conventions. This provides immediate operational guidance and aligns teams on the current project structure.

Can I use a markdown body with frontmatter to contextualize development tasks?

Yes, you can use a markdown body with frontmatter containing a name and description to contextualize development tasks. This setup allows the project context to load directly into the environment for quick team reference.

Does this context approach work for tracking sprint status and known bugs?

Yes, this context approach works for tracking sprint status and known bugs by aggregating them into a quick reference format. Teams can review this context before starting work to align on sprint goals and current issues.

When do I need a centralized file map and conventions reference for software engineering?

You need a centralized file map and conventions reference for software engineering when onboarding new contributors or validating decisions against the project plan. It provides concise, up-to-date context for feature planning and sprint reviews.