feature

Name: feature
Author: eduwxyz

15stars1forks

How to install feature?

eduwxyz/my-awesome-skills/feature

$npx -y skills add eduwxyz/my-awesome-skills --skill feature

Installs into the current project.

Summary

Kick off the full feature workflow — interview-to-spec, optional spec-approach, tdd, verify, then review — when starting a new feature from scratch. Thin orchestrator: confirms intent in one sentence, then hands off to the first stage and lets each downstream skill activate on it

Files · 1

View on GitHub

SKILL.md

1	# Feature
2
3	The orchestrated path for building a new feature, from idea to PR-ready. This skill is a thin dispatcher — it confirms intent and hands off. Each downstream skill activates on its own.
4
5	## When to use this
6
7	You want the full SDD pipeline in order without having to remember each step.
8
9	## When NOT to use this
10
11	- Bug fix. Use `diagnose` instead.
12	- Trivial change that doesn't need a spec (one-line config, doc tweak). Edit directly.
13	- Already partway through a workflow. Resume at the relevant stage by invoking the matching skill (`interview-to-spec`, `spec-approach`, `tdd`, `verify`).
14
15	## The pipeline
16
17	You will pass through these stages in order:
18
19	1. `interview-to-spec` — hand off. The skill conducts the interview and writes `spec/<slug>.md` (Goal, Behaviors, Acceptance criteria, Out of scope, Edge cases).
20
21	2. `spec-approach` (optional) — when the spec is written, judge whether the HOW is non-trivial:
22	- Multiple modules touched?
23	- Multiple viable approaches?
24	- Architectural decision required?
25	- Schema or API changes?
26
27	If yes, invoke `spec-approach` to append `## Approach` to the spec. If no, skip and move on.
28
29	3. `tdd` — hand off. Red-green-refactor against the spec's Behaviors + Acceptance criteria. The skill itself ensures `.agents/tdd/test-command.txt` is configured on first run, and its Stop hook will gate on green tests + a pass through `simplify`.
30
31	4. `verify` — hand off. Maps every AC to a green test. If gaps exist, the skill auto-iterates with `tdd` until clean. Will not return until the verdict is `Ready`.
32
33	5. `review` (built-in) — when verify reports `Ready`, hand off for code review. Then open the PR.
34
35	## How handoff works
36
37	This skill ends as soon as you invoke `interview-to-spec`. It does not stay active across the pipeline. Each downstream skill activates from its own trigger phrasing as the conversation progresses.
38
39	If you stop the session midway and resume later, invoke the next stage's skill directly — do not re-invoke `feature`.
40
41	## What to do first
42
43	Confirm the user's intent in one sentence ("Kicking off the feature workflow for `<short-description>`."), then immediately invoke `interview-to-spec`. Do not attempt the interview yourself — that is `interview-to-spec`'s job.

People who liked this also viewed

6 picks

Type

feature

15stars1forks

View on GitHub

How to install feature?

eduwxyz/my-awesome-skills/feature

$npx -y skills add eduwxyz/my-awesome-skills --skill feature

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Feature
2
3	The orchestrated path for building a new feature, from idea to PR-ready. This skill is a thin dispatcher — it confirms intent and hands off. Each downstream skill activates on its own.
4
5	## When to use this
6
7	You want the full SDD pipeline in order without having to remember each step.
8
9	## When NOT to use this
10
11	- Bug fix. Use `diagnose` instead.
12	- Trivial change that doesn't need a spec (one-line config, doc tweak). Edit directly.
13	- Already partway through a workflow. Resume at the relevant stage by invoking the matching skill (`interview-to-spec`, `spec-approach`, `tdd`, `verify`).
14
15	## The pipeline
16
17	You will pass through these stages in order:
18
19	1. `interview-to-spec` — hand off. The skill conducts the interview and writes `spec/<slug>.md` (Goal, Behaviors, Acceptance criteria, Out of scope, Edge cases).
20
21	2. `spec-approach` (optional) — when the spec is written, judge whether the HOW is non-trivial:
22	- Multiple modules touched?
23	- Multiple viable approaches?
24	- Architectural decision required?
25	- Schema or API changes?
26
27	If yes, invoke `spec-approach` to append `## Approach` to the spec. If no, skip and move on.
28
29	3. `tdd` — hand off. Red-green-refactor against the spec's Behaviors + Acceptance criteria. The skill itself ensures `.agents/tdd/test-command.txt` is configured on first run, and its Stop hook will gate on green tests + a pass through `simplify`.
30
31	4. `verify` — hand off. Maps every AC to a green test. If gaps exist, the skill auto-iterates with `tdd` until clean. Will not return until the verdict is `Ready`.
32
33	5. `review` (built-in) — when verify reports `Ready`, hand off for code review. Then open the PR.
34
35	## How handoff works
36
37	This skill ends as soon as you invoke `interview-to-spec`. It does not stay active across the pipeline. Each downstream skill activates from its own trigger phrasing as the conversation progresses.
38
39	If you stop the session midway and resume later, invoke the next stage's skill directly — do not re-invoke `feature`.
40
41	## What to do first
42
43	Confirm the user's intent in one sentence ("Kicking off the feature workflow for `<short-description>`."), then immediately invoke `interview-to-spec`. Do not attempt the interview yourself — that is `interview-to-spec`'s job.

People who liked this also viewed

6 picks

Type