This was generated by AI during triage.
Parent
docs/issues/feature-runner/PRD.md
What to build
Add a ## Quick start section near the top of .claude/skills/implement-feature/SKILL.md, immediately after the opening paragraph and before ## Steps. The section should show the three realistic invocation patterns as annotated bullet points, so a user can orient themselves before reading the full step-by-step.
The three patterns:
- Named run —
/implement-feature pr-review-doc-context-enrichment — targets a specific feature slug directly
- Auto-select —
/implement-feature with no argument — scans docs/issues/ and picks the first fully ready-for-agent feature alphabetically
- Overnight loop —
/loop /implement-feature — composes with the /loop skill to drain the queue unattended; the runner emits LOOP_COMPLETE when no qualifying feature remains, which terminates the loop
No separate EXAMPLES.md file is needed — docs/agents/feature-runner.md already covers lifecycle and mechanics in prose.
Acceptance criteria
Blocked by
#80
Comments
This was generated by AI during triage.
Agent Brief
Category: enhancement
Summary: Add a ## Quick start section to the implement-feature skill so users can orient themselves before reading the full 7-step workflow.
Current behavior:
The implement-feature SKILL.md opens with a one-paragraph description and jumps directly into ## Steps. A user invoking the skill for the first time must read all 7 steps to understand the three basic usage patterns.
Desired behavior:
A ## Quick start section appears between the opening paragraph and ## Steps. It contains exactly three bullet points — one per invocation pattern — each with a concrete example command and a one-line description of what it does. No new files are created.
Key interfaces:
- The
implement-feature SKILL.md top-level structure: frontmatter → opening paragraph → ## Quick start → ## Steps
- The three invocation patterns (content defined in
## What to build) must match the behavior already implemented in Step 0 of SKILL.md
Acceptance criteria:
Out of scope:
- Changing any step logic or the 7-step structure
- Creating an
EXAMPLES.md file
- Updating
docs/agents/feature-runner.md
PRD: docs/issues/feature-runner/PRD.md
Migrated from: docs/issues/feature-runner/11-quick-start.md (source removed after migration)
Touched by PRs: #25, #32
Parent
docs/issues/feature-runner/PRD.mdWhat to build
Add a
## Quick startsection near the top of.claude/skills/implement-feature/SKILL.md, immediately after the opening paragraph and before## Steps. The section should show the three realistic invocation patterns as annotated bullet points, so a user can orient themselves before reading the full step-by-step.The three patterns:
/implement-feature pr-review-doc-context-enrichment— targets a specific feature slug directly/implement-featurewith no argument — scansdocs/issues/and picks the first fullyready-for-agentfeature alphabetically/loop /implement-feature— composes with the/loopskill to drain the queue unattended; the runner emitsLOOP_COMPLETEwhen no qualifying feature remains, which terminates the loopNo separate
EXAMPLES.mdfile is needed —docs/agents/feature-runner.mdalready covers lifecycle and mechanics in prose.Acceptance criteria
## Quick startsection exists inSKILL.mdbetween the opening paragraph and## StepsEXAMPLES.md)SKILL.mdis unchangedBlocked by
#80
Comments
Agent Brief
Category: enhancement
Summary: Add a
## Quick startsection to theimplement-featureskill so users can orient themselves before reading the full 7-step workflow.Current behavior:
The
implement-featureSKILL.md opens with a one-paragraph description and jumps directly into## Steps. A user invoking the skill for the first time must read all 7 steps to understand the three basic usage patterns.Desired behavior:
A
## Quick startsection appears between the opening paragraph and## Steps. It contains exactly three bullet points — one per invocation pattern — each with a concrete example command and a one-line description of what it does. No new files are created.Key interfaces:
implement-featureSKILL.md top-level structure: frontmatter → opening paragraph →## Quick start→## Steps## What to build) must match the behavior already implemented in Step 0 of SKILL.mdAcceptance criteria:
## Quick startsection exists in SKILL.md between the opening paragraph and## Steps/loopEXAMPLES.mdor other companion files)Out of scope:
EXAMPLES.mdfiledocs/agents/feature-runner.mdPRD:
docs/issues/feature-runner/PRD.mdMigrated from:
docs/issues/feature-runner/11-quick-start.md(source removed after migration)Touched by PRs: #25, #32