groove-work-spec

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use $ARGUMENTS as the spec topic if provided.

如果提供了$ARGUMENTS，则将其用作规范主题。

A complete outcome spec that defines what to build and how to verify it — the agent determines the procedure.

一份完整的产出规范，定义需要构建的内容以及验证方式——具体流程由Agent决定。

Spec file contains:

规范文件包含：

Sanitize topic for use as filename — strip path separators, special characters, and traversal patterns (
```
../
```
)
Read
```
memory:
```
from
```
.groove/index.md
```
for base path; save spec to
```
<memory>/specs/
```
Ensure
```
<memory>/specs/
```
exists (create if missing)
Research codebase first (use Explore agent)
Interview user for decisions, edge cases, testing approach, scope
Assess scope: if the work has natural seams (independent components, sequential phases, separable concerns), recommend splitting into a parent spec with child specs
- Parent spec: Overview of the full feature, links to child specs, execution order if sequential
- Child specs: Each self-contained with its own Overview, Decisions, Steps, Edge Cases
- Naming:
```
<topic>.md
```
  for single specs,
```
<topic>/index.md
```
  +
```
<topic>/01-<part>.md
```
  for split specs
- User decides: Present the split recommendation with rationale, user confirms or overrides
Write spec in isolated context (use general-purpose agent)
Verify all required sections exist before completing
Reference actual codebase patterns, not generic advice