tessl-test

Package a standalone skill into a Tessl tile for versioning, distribution, and evaluation. Creates tile manifest, validates directory structure, and ensures skill format compliance. Use when asked to "convert to tile", "package this skill", "create a tessl tile", "wrap skill in tile", or before running evals on a skill not yet in a tile.

Implements a feature by executing a plan phase-by-phase — writes tests first, runs them red, then implements code to make them green, then validates nothing is broken. Use when you have a plan from /draft and are ready to implement, build, develop, create, or write code for a feature using TDD.

Implement phase of RPI methodology. Executes beads-driven task graph using isolated agents for test-first discipline. Use when executing an implementation plan from the draft skill.

Implement phase of RPI methodology. Executes beads-driven task graph using isolated agents for test-first discipline. Use when executing an implementation plan from the draft skill.

Generate evaluation scenarios for Tessl tiles to measure skill effectiveness. Creates inventory of instructions from the skill, test cases with success criteria, and validates skill coverage. Use when asked to "generate evals", "create evaluation scenarios", "test this skill", "measure skill value", or "prepare for tessl publish".

Transforms a research artifact or feature topic into a compact implementation plan with task breakdown, dependency mapping, test specifications, and acceptance criteria. Use when planning a non-trivial feature, designing architecture, writing a technical spec, or breaking down implementation steps before coding. Produces a phased plan with Agent Context blocks and a beads task graph for incremental execution.

Plan phase of RPI methodology. Consumes research artifact or topic and produces compact implementation plan with test specs and Agent Context blocks. Use after research or to start planning a non-trivial feature.

Plan phase of RPI methodology. Consumes research artifact or topic and produces compact implementation plan with test specs and Agent Context blocks. Use after research or to start planning a non-trivial feature.

Applies hexagonal (ports & adapters) architecture. Use when designing application structure, separating domain from infrastructure, creating testable boundaries, or when user mentions ports, adapters, hexagonal, or clean architecture.

Guided pair-programming mode where Claude teaches rather than solves — asking guiding questions, providing hints, explaining concepts, and reviewing user-written code instead of writing solutions. Use when the user wants to learn while building: says "teach me", "help me understand", "guide me", "walk me through", "mentor me", "don't just give me the answer", "learning mode", or invokes /pair.

Guided pair-programming mode where Claude teaches rather than writes code, ensuring engineers learn while building

Guided pair-programming mode where Claude teaches rather than writes code, ensuring engineers learn while building

Restructures code by extracting methods, renaming symbols, simplifying conditionals, removing duplication, and eliminating dead code — while running tests before and after each change to ensure behavior is preserved. Invoke immediately when user mentions refactor, refactoring, clean up, restructure, simplify, technical debt, code smell, DRY violations, or when code is messy, complex, or hard to maintain.

Refactoring process with test safety. Invoke immediately when user or document mentions refactoring, or proactively when code gets too complex or messy.

Refactoring process with test safety. Invoke immediately when user or document mentions refactoring, or proactively when code gets too complex or messy.

Post-session reflection skill for review session, retrospective, or session summary. Reads recent git history, artifacts, and context files to extract learnings and produce improvement proposals for skills, CLAUDE.md, hooks, and plan templates. Use after any substantive session to capture what did we learn and embed improvements back into codebase context.

Post-session reflection skill. Reads recent git history, artifacts, and context files to extract learnings and produce improvement proposals for skills, CLAUDE.md, hooks, and plan templates. Use after any substantive session.

Post-session reflection skill. Reads recent git history, artifacts, and context files to extract learnings and produce improvement proposals for skills, CLAUDE.md, hooks, and plan templates. Use after any substantive session.

Explore a codebase and research external patterns before planning a new feature. Spawns parallel subagents for codebase investigation and web research, then synthesizes findings into a compact artifact (~200 lines) for user review. Use when starting a non-trivial feature, investigating unfamiliar code, or evaluating libraries and architectural approaches.

Research phase of RPI methodology. Spawns parallel subagents for codebase exploration AND web/pattern research, then synthesizes findings for user review. Produces compact research artifact. Use at the start of non-trivial features.