trove-spec
Product spec writing skill. Generates structured feature specifications with user stories, acceptance criteria, and technical considerations.
- License 许可
- MIT
- 所属仓库
- bravew/trove
- 最近更新
- 2026-11-12
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- trove-spec
- metadata
- { "trove-category": "product", "trove-category-label": "Product" }
- description
- Product spec writing skill. Generates structured feature specifications with user stories, acceptance criteria, and technical considerations.
- when_to_use
- product spec; feature spec; write a spec
02 资源文件 1
- 其他SKILL.md.tmpl1.3 KB
03 SKILL.md 正文
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run build:skills -->
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Product Spec Template
Structure
# Feature: [Name]
## Problem Statement
What problem does this solve? Who experiences it? How severe is it?
## Proposed Solution
High-level description of the solution.
## User Stories
- As a [role], I want to [action] so that [benefit]
## Acceptance Criteria
- [ ] Given [context], when [action], then [outcome]
## Out of Scope
What this feature explicitly does NOT include.
## Technical Considerations
- Dependencies on other systems/features
- Data model changes
- API changes
- Performance implications
## Success Metrics
| Metric | Current | Target | Measurement |
|--------|---------|--------|-------------|
## Timeline
| Phase | Scope | Duration |
|-------|-------|----------|
## Open Questions
- [ ] Question 1
- [ ] Question 2
Best Practices
- Keep specs under 2 pages (focus on what matters)
- Write acceptance criteria as testable assertions
- Include "Out of Scope" to prevent scope creep
- Link to designs/mockups rather than describing visuals
04 同仓库更多 Skills
using-trove
Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.
trove-write-skill
Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.
trove-worktree
Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.
trove-why
Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for "why does X work this way", "why did we pick Y", regressions, and postmortems. Use trove-explain for how it works now.
trove-verify
Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.
trove-unslop
Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.