new-feature

Name: new-feature
Author: dan-the-dev

27stars0forks

How to install new-feature?

dan-the-dev/xp-developer-skills/new-feature

$npx -y skills add dan-the-dev/xp-developer-skills --skill new-feature

Installs into the current project.

Summary

Slice a whole capability into ordered releasable increments (increment backlog in increments/<stem>.md). Delegate each slice to skills/new-increment — do not implement slices yourself. Use for an entire feature or epic (e.g. full FizzBuzz), not for implementing one increment.

Files · 1

View on GitHub

SKILL.md

1	# New feature (increment planning)
2
3	## Mission
4
5	Plan a whole feature as ordered, releasable increments. Do not implement slices in this skill — each open line is delivered by `skills/new-increment` (or the `new-increment` subagent) in a separate invocation.
6
7	First step: create `increments/<feature-stem>.md` (see [references/increment-backlog.md](references/increment-backlog.md)).
8
9	Feature complete when every in-scope increment is `[x]` on that backlog — each line completed via `skills/new-increment`, not by continuing in this session.
10
11	---
12
13	## Workflow
14
15	Shared delivery rules: [`docs/delivery-process.md`](../../docs/delivery-process.md) (planning role — §1, §10).
16
17	1. Clarify capability and whole-feature definition of done.
18	2. If feasibility unknown → `skills/spike` on `spike/…` branch; promote before slicing.
19	3. Write ordered increment lines in `increments/<stem>.md` (all `[ ]` initially). Optionally note expected test layers per line (see [`test-strategy-selection.md`](../../docs/test-strategy-selection.md) §2) — e.g. “mutation likely”, “contract at boundary”.
20	4. Stop. Hand off the first open line to `skills/new-increment` (subagent or new chat).
21	5. After each increment completes elsewhere, repeat planning-only check: next open line → hand off again.
22
23	Optional: create `test-lists/<feature-stem>.md` with empty `## <increment-slug>` headings as a skeleton — no behavior lines or `[x]` until new-increment runs.
24
25	See [examples/fizzbuzz-increments.md](examples/fizzbuzz-increments.md).
26
27	---
28
29	## What this skill may edit
30
31	\| Allowed \| Forbidden \|
32	\|---------\|-----------\|
33	\| `increments/<stem>.md` \| `src/`, `test/`, `tests/` \|
34	\| Optional skeleton `test-lists/<feature-stem>.md` (headings only) \| `acceptance-examples/` (created per increment in new-increment) \|
35	\| Docs clarifying scope \| Production or test code \|
36
37	---
38
39	## Composition
40
41	\| Need \| Skill \|
42	\|------\|--------\|
43	\| One slice delivery \| `skills/new-increment` \|
44	\| Untested area \| `skills/legacy-testing` (before or per increment) \|
45	\| Green prep \| `skills/refactoring` \|
46	\| Unknown tech \| `skills/spike` \|
47
48	This skill does not run ATDD/TDD or mark increments `[x]` from implementation work.
49
50	---
51
52	## User opt-in: implement all increments
53
54	Only if the user explicitly asks to implement the full backlog in one go:
55
56	- Still use one increment’s discipline at a time (RED gates, one backlog `[x]` per slice).
57	- Prefer invoking `new-increment` repeatedly over batching “increments 2–7.”
58	- Default remains: one increment per subagent/session.
59
60	---
61
62	## Anti-patterns
63
64	- One backlog line for the entire feature
65	- Implementing code or tests in the new-feature session
66	- Marking multiple `[ ]` → `[x]` without a new-increment pass each
67	- Skipping `new-increment` (no scoped TDD per slice)
68	- No on-disk `increments/` file
69	- Creating many per-increment markdown files during planning
70
71	See [references/anti-patterns.md](references/anti-patterns.md).
72
73	---
74
75	## Additional resources
76
77	- [references/increment-backlog.md](references/increment-backlog.md)
78	- [references/slicing-increments.md](references/slicing-increments.md)
79	- [references/anti-patterns.md](references/anti-patterns.md)
80	- [examples/fizzbuzz-increments.md](examples/fizzbuzz-increments.md)

People who liked this also viewed

6 picks

Type

new-feature

27stars0forks

View on GitHub

How to install new-feature?

dan-the-dev/xp-developer-skills/new-feature

$npx -y skills add dan-the-dev/xp-developer-skills --skill new-feature

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# New feature (increment planning)
2
3	## Mission
4
5	Plan a whole feature as ordered, releasable increments. Do not implement slices in this skill — each open line is delivered by `skills/new-increment` (or the `new-increment` subagent) in a separate invocation.
6
7	First step: create `increments/<feature-stem>.md` (see [references/increment-backlog.md](references/increment-backlog.md)).
8
9	Feature complete when every in-scope increment is `[x]` on that backlog — each line completed via `skills/new-increment`, not by continuing in this session.
10
11	---
12
13	## Workflow
14
15	Shared delivery rules: [`docs/delivery-process.md`](../../docs/delivery-process.md) (planning role — §1, §10).
16
17	1. Clarify capability and whole-feature definition of done.
18	2. If feasibility unknown → `skills/spike` on `spike/…` branch; promote before slicing.
19	3. Write ordered increment lines in `increments/<stem>.md` (all `[ ]` initially). Optionally note expected test layers per line (see [`test-strategy-selection.md`](../../docs/test-strategy-selection.md) §2) — e.g. “mutation likely”, “contract at boundary”.
20	4. Stop. Hand off the first open line to `skills/new-increment` (subagent or new chat).
21	5. After each increment completes elsewhere, repeat planning-only check: next open line → hand off again.
22
23	Optional: create `test-lists/<feature-stem>.md` with empty `## <increment-slug>` headings as a skeleton — no behavior lines or `[x]` until new-increment runs.
24
25	See [examples/fizzbuzz-increments.md](examples/fizzbuzz-increments.md).
26
27	---
28
29	## What this skill may edit
30
31	\| Allowed \| Forbidden \|
32	\|---------\|-----------\|
33	\| `increments/<stem>.md` \| `src/`, `test/`, `tests/` \|
34	\| Optional skeleton `test-lists/<feature-stem>.md` (headings only) \| `acceptance-examples/` (created per increment in new-increment) \|
35	\| Docs clarifying scope \| Production or test code \|
36
37	---
38
39	## Composition
40
41	\| Need \| Skill \|
42	\|------\|--------\|
43	\| One slice delivery \| `skills/new-increment` \|
44	\| Untested area \| `skills/legacy-testing` (before or per increment) \|
45	\| Green prep \| `skills/refactoring` \|
46	\| Unknown tech \| `skills/spike` \|
47
48	This skill does not run ATDD/TDD or mark increments `[x]` from implementation work.
49
50	---
51
52	## User opt-in: implement all increments
53
54	Only if the user explicitly asks to implement the full backlog in one go:
55
56	- Still use one increment’s discipline at a time (RED gates, one backlog `[x]` per slice).
57	- Prefer invoking `new-increment` repeatedly over batching “increments 2–7.”
58	- Default remains: one increment per subagent/session.
59
60	---
61
62	## Anti-patterns
63
64	- One backlog line for the entire feature
65	- Implementing code or tests in the new-feature session
66	- Marking multiple `[ ]` → `[x]` without a new-increment pass each
67	- Skipping `new-increment` (no scoped TDD per slice)
68	- No on-disk `increments/` file
69	- Creating many per-increment markdown files during planning
70
71	See [references/anti-patterns.md](references/anti-patterns.md).
72
73	---
74
75	## Additional resources
76
77	- [references/increment-backlog.md](references/increment-backlog.md)
78	- [references/slicing-increments.md](references/slicing-increments.md)
79	- [references/anti-patterns.md](references/anti-patterns.md)
80	- [examples/fizzbuzz-increments.md](examples/fizzbuzz-increments.md)

People who liked this also viewed

6 picks

Type