A curated library of 12 language-agnostic planning skills and 4 personas for technical project management, product planning, and agile execution.
91
94%
Does it follow best practices?
Impact
91%
1.16xAverage score across 16 eval scenarios
Passed
No known issues
Focus on what and why, not how. No code until the PRD is approved.
/tasks/prd-<slug>.md.Focus exclusively on WHAT and WHY, not HOW.
DO NOT include code, pseudo-code, SQL, class names, or method signatures.
DO NOT generate tasks or code until the PRD is explicitly approved.Load these files only when their specific content is needed:
answer.md), create the PRD there. When no output path is specified, default to /tasks/prd-<feature-slug>.md (kebab-case). State the path.generate-tasks once this PRD is approved."After creating the PRD, surface the file path and request explicit approval.
| Skill | When to chain |
|---|---|
| generate-tasks | After PRD approved, to derive implementation steps |
| plan-tickets | When tracker tickets are needed from the approved PRD scope |
.tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
skills
analysis
requirements-clarifier
backlog
prioritize-backlog
ceremony
create-retrospective
plan-sprint
infrastructure
github-issue
prd
create-prd
review-prd
task-management
estimate-tasks
generate-tasks
plan-tickets