trd
Skill19 starsChanged 2 months agoMITView on GitHub
WHAT — Draft and review a Technical Requirements Document (TRD) using the template, typically
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Do not dump the full external template into this skill.
- Distinctive: line 35
Do not skip risks and testing when the TRD is a handoff artifact.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TRD — Technical Requirements (WHAT)
Template: references/default-template.md — local reference, kept up to date with the standard structure.
Default guardrails (before any final content)
- Apply
output-handshake: confirm where the final TRD will live and that a human will review. - Then follow the steps below.
When to use
- A PRD is approved (or the task is technical-only) and the team needs design-level agreement before build.
- You need API/data contracts, component boundaries, and test strategy aligned to standards.
- A client doc hub with PRD/TRD cross-links requires matching document structure.
Instructions
- Open the TRD template (
references/default-template.md). Align sections: Scope, Architecture overview, Data model / API contracts, Technical decisions (link ADRs and spikes), Dependencies, Risks & constraints, Testing strategy, Implementation plan. - Map from PRD: user stories and AC from the PRD should appear as addressed in the TRD with clear technical response; if no PRD exists, state that explicitly and list assumptions.
- For ADRs that block or explain design, use
adrto structure the decision, then link the task or ADR in the forge per your engagement. - Delegate repo facts to
assistant(conventions, CI, existing patterns); cite sources. - For ticket updates, use the appropriate tool (
clickup-cli,jira-*, etc.); keep task comments short with links to the Doc (perworkflow-generic-project).
What not to do
- Do not dump the full external template into this skill; use
references/default-template.mdas the local canonical reference. - Do not skip risks and testing when the TRD is a handoff artifact.
References
output-handshake— destination and reviewreferences/default-template.md— local TRD templatereferences/example-unified-api.md— TRD example for a full API migration (see PRD link in that file)references/example-api-migration.md— detailed TRD example with phases, architecture, and testing strategyprd— when work starts from product requirementsspike— research findings used as design evidenceadr— decision records linked from the TRDdevelopment-workflow— validation and traceability expectationsincident— failure handling / incident implications when relevantworkflow-generic-project— delivery gates and traceabilityclickup-cli,jira-*— ticket / comment operations (per engagement)
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- arfar-x/agent-skills★ 13same name
- Sumit189/claude-codes★ 1same name
- ihyonoo/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository106 other files it gives its agents.
- AGENTS.mdAGENTS.md
- reviewSkill
- mcp-auditSkill
- owasp-agentic-reviewSkill
- supply-chain-auditSkill
- threat-modelingSkill
- architecture-diagramSkill
- c4-modelSkill
- aws-well-architected-reviewSkill
- cloud-design-patternsSkill
- assistantSkill
- dev-companionSkill
- onboardingSkill
- output-handshakeSkill
- pr-fallbackSkill
- projectSkill
- workspace-knowledge-syncSkill
- workspaceSkill
- dbt-validationSkill
- snowflake-validationSkill
- adrSkill
- agreementSkill
- bugSkill
- decision-logSkill
- development-workflowSkill
- epicSkill
- incidentSkill
- management-unit-assessmentSkill
- meeting-minutesSkill
- planningSkill
- prdSkill
- project-assessment-evidenceSkill
- project-assessmentSkill
- spikeSkill
- taskSkill
- technical-unit-assessmentSkill
- user-storySkill
- workflow-client-bootstrapSkill
- workflow-generic-projectSkill
- work-itemSkill
- bragSkill
- brag-slimSkill
- design-assessmentSkill
- design-improvementSkill
- figma-code-connect-componentsSkill
- figma-create-design-system-rulesSkill
- figma-create-new-fileSkill
- figma-implement-designSkill
- figmaSkill
- frontend-design-reviewSkill
- frontend-designSkill
- scroll-worldSkill
- web-design-guidelinesSkill
- fix-merge-conflictsSkill
- gh-address-commentsSkill
- gh-contribution-plannerSkill
- gh-fix-ciSkill
- github-cli-workflowSkill
- gitlab-cli-workflowSkill
- worktreeSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.