trellis-before-dev

Read .trellis/spec guidelines and create a guided task plan before implementation.

45|9|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Tendo33/IdeaGo --skill trellis-before-dev-tendo33
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/Tendo33/IdeaGo/tree/main/.agents/skills/trellis-before-dev
Command: npx skills add https://github.com/Tendo33/IdeaGo --skill trellis-before-dev-tendo33

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool ensures developers consult and inject project-wide guidelines from .trellis/spec before starting work, reducing drift and rework.

Core Features & Use Cases

  • Reads and interprets spec indexes and pre-development checklists to surface the applicable standards for a given package.
  • Integrates shared thinking guides to align task approaches across teams and modules.
  • Use Case: You are starting work on a new package like docs-site/ and need to refresh conventions before implementation to ensure consistency.

Quick Start

Read the relevant development guidelines before starting your task.

Frequently Asked Questions about trellis-before-dev

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

FAQPage Schema
How do I enforce pre-development coding standards before starting a new package?

Pre-development checklists consolidate project-specific rules into a guided task plan, ensuring developers consult applicable standards and shared guides before coding to maintain consistency across modules.

What is the best way to align task approaches across teams and modules?

The best way to align task approaches is by integrating shared thinking guides with spec indexes, which creates a guided task plan that enforces consistency across teams during planning and coding.

How do I read and apply development guidelines from a spec index?

You read development guidelines from a spec index by parsing the pre-development indexes and checklists, which surface the applicable standards for a given package to inject into your workflow before coding.

When do I need to consult pre-development checklists for my project?

You need to consult pre-development checklists when starting work on a new package or task, as this surfaces the applicable standards required to refresh conventions and prevent rework before implementation begins.

Does this workflow require a specific directory structure to apply coding standards?

Yes, the workflow requires a specific directory structure, as it discovers and consolidates project-specific development guidelines from a .trellis/spec directory before starting implementation to enforce consistency.