Skill reference
The 13 skills defined in skills/*/SKILL.md. Edit the skill file, not this page.
| Skill | Description |
|---|---|
team-architecture | Technical architecture design methodology. Data model, API contract, module boundaries, technology selection rationale, scalability. The playbook of the architect role. |
team-backlog | Break the PRD into tracer-bullet tickets, vertical slices with acceptance criteria and blocking edges, ordered into .team/03-backlog.md. The playbook of the po role. |
team-brand | Brand and logo design methodology for this team. Brief, research, concepts, mark types, geometric SVG construction, optical refinement, small-size and one-colour testing, colour, typography, lockups, favicon and app-icon set, brand guide and presentation. The playbook of the brand role. |
team-build | The build and TDD playbook for this team. Red-green-refactor, test-first vertical slices, seams, test pyramid, mocking at boundaries, deterministic tests and definition of done. |
team-docs | Technical documentation writing methodology. README, usage guide, API documentation and architecture note. The playbook of the docs role. |
team-market-research | Market, competitor and user research methodology. Source verification, competitor table, niche analysis and risk assessment. The playbook of the analyst role. |
team-marketing | Marketing and launch methodology. Positioning, message framework, channel plan, launch copy, measurable metrics. The playbook of the marketing role. |
team-memory | Use when an agent starts or finishes a task, reads or writes .team/memory, records a decision, resumes an interrupted run, or compacts project memory. Covers INDEX.md, role logs, decision files, archives, run checkpoints and the no-secrets rule for OpenCode Team. |
team-prd | Product requirements document (PRD) writing methodology. Scope, out of scope, user stories, acceptance criteria and success metrics. The playbook of the pm role. |
team-qa | Test strategy and quality assurance methodology. Acceptance criterion -> test conversion, edge cases, e2e coverage. The playbook of the qa role. |
team-release | Version management and deployment methodology. Semver, CHANGELOG, CI/CD, deployment steps, environment variables, rollback plan. The playbook of the devops role. |
team-security-review | Security review methodology. Authentication, authorization, input validation, secret management, dependency scanning and finding reporting. The playbook of the security role. |
team-ux | UX design specification writing. Screen flows, state inventory, component list, accessibility and mobile behavior. The playbook of the ux role. |