Agent skills by task
Agent Skills for Planning, Specs and Tickets
Most agent mistakes start before the first line of code. Planning skills make the agent interview you, agree on terms, write a spec and split it into tickets, so the build matches what you actually meant.
- skills
- 9
- packs
- 3
The skills
In the order we would try them
-
/brainstormingDesign-first brainstorming before any buildClarifies what you want and why, then gets a design approved before building.
-
/grill-with-docsPlan interviews that build a project glossaryInterviews you about a plan and records agreed terms and decisions as glossary and ADRs.
-
/grill-meInterviews you hard about any plan or idea, including non-code ones.
-
/to-specTurns what you already discussed into a spec on your issue tracker.
-
/writing-plansTurns an approved spec into small tasks with file paths, code and checks.
-
/to-ticketsSplits a plan or spec into small tickets that state what blocks what.
-
/wayfinderPlans work too large for one session as a map of decision tickets.
-
/domain-modelingBuilds and maintains the project's glossary and architecture decision records during design talks.
-
/doc-coauthoringLeads a staged workflow for drafting specs, proposals and other structured documents with the user.
Questions
Why would I want the agent to ask me questions?
Every open decision the agent fills in by itself is a guess. Questioning skills surface those decisions up front, when changing them costs a sentence instead of a rewrite.
Do planning skills need an issue tracker?
Some do: /to-spec and /to-tickets write to the tracker you configure. /brainstorming and /grill-with-docs work with plain files in the repo.
Skills for other jobs
Lists picked by trendhub from public skill packs. Each skill lives in its author’s repository; read the current text there before installing.