Prompt file imported from zan-ia/zan-visual-novel (.github/prompts/start-feature.prompt.md). Copyright stays with the author.

--- description: 'Initiates the new feature pipeline. The orchestrator classifies the feature, invokes workflow analysis, then coordinates the Plan→Implement→Review cycle via specialist agents.' argument-hint: "Describe the new feature (e.g., 'Add a pricing section with 3 plans...')" agent: 'orchestrator'

Start Feature Pipeline

Name: start-feature
Author: zan-ia

The orchestrator receives your feature request and orchestrates the complete development pipeline. See .github/instructions/pipeline-workflow.instructions.md.

Procedure

1. Analyze (Engineer) Feature

If the user's description is incomplete, use vscode_askQuestions to clarify:

- header: "Feature Scope"
  question: "What are the boundaries of this feature?"
- header: "Acceptance Criteria"
  question: "How will we know the feature is ready?"
- header: "Priority"
  question: "Does this feature replace something existing or is it entirely new?"
  options:
    - label: "Entirely new feature"
    - label: "Replaces/extends something existing"
    - label: "Variation of an existing component"

2. Create Workflow Artifact + Issue

Create a GitHub issue in the project with:

Title: feat: [short feature description]

Body:

### Motivation

[Why is this feature needed? What problem does it solve?]

### Description

[What will be implemented, in detail]

### Acceptance Criteria

- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3

### Reference Design

[Links to inspirations, mockups, or similar components on the site]

### Affected Components

- [list of existing components that will be modified]

3. Hand Off to Orchestrator

🛑 STOP and wait. Present the issue to the user and wait for explicit approval before proceeding.

After approval, execute the complete pipeline:

Create branch feat/short-description from main
Invoke planner (subagent) to analyze the codebase and generate an implementation plan
Invoke implementer (subagent) to build the feature
Invoke code-reviewer (subagent) to validate
If critical/major → re-plan (max. 3x)
Commit with feat: + push
Create PR with Closes #N
HITL — wait for PR review

Commit Template (Feature)

feat(scope): add feature description

Brief description of what was implemented.
Key decisions and patterns used.

Closes #N

References

Complete pipeline: .github/instructions/pipeline-workflow.instructions.md
Tool usage: .github/instructions/tool-usage.instructions.md
Code conventions: AGENTS.md

--- description: 'Initiates the new feature pipeline. The orchestrator classifies the feature, invokes workflow analysis, then coordinates the Plan→Implement→Review cycle via specialist agents.' argument-hint: "Describe the new feature (e.g., 'Add a pricing section with 3 plans...')" agent: 'orchestrator' --- # Start Feature Pipeline The orchestrator receives your feature request and orchestrates the complete development pipeline. See `.github/instructions/pipeline-workflow.instructions.md`. ## Procedure ### 1. Analyze (Engineer) Feature If the user's description is incomplete, use `vscode_askQuestions` to clarify: ``` - header: "Feature Scope" question: "What are the boundaries of this feature?" - header: "Acceptance Criteria" question: "How will we know the feature is ready?" - header: "Priority" question: "Does this feature replace something existing or is it entirely new?" options: - label: "Entirely new feature" - label: "Replaces/extends something existing" - label: "Variation of an existing component" ``` ### 2. Create Workflow Artifact + Issue Create a GitHub issue in the project with: **Title:** `feat: [short feature description]` **Body:** ```markdown ### Motivation [Why is this feature needed? What problem does it solve?] ### Description [What will be implemented, in detail] ### Acceptance Criteria - [ ] Criterion 1 - [ ] Criterion 2 - [ ] Criterion 3 ### Reference Design [Links to inspirations, mockups, or similar components on the site] ### Affected Components - [list of existing components that will be modified] ``` ### 3. Hand Off to Orchestrator 🛑 **STOP and wait.** Present the issue to the user and wait for explicit approval before proceeding. After approval, execute the complete pipeline: 1. Create branch `feat/short-description` from `main` 2. Invoke `planner` (subagent) to analyze the codebase and generate an implementation plan 3. Invoke `implementer` (subagent) to build the feature 4. Invoke `code-reviewer` (subagent) to validate 5. If critical/major → re-plan (max. 3x) 6. Commit with `feat:` + push 7. Create PR with `Closes #N` 8. HITL — wait for PR review --- ## Commit Template (Feature) ``` feat(scope): add feature description Brief description of what was implemented. Key decisions and patterns used. Closes #N ``` --- ## References - Complete pipeline: `.github/instructions/pipeline-workflow.instructions.md` - Tool usage: `.github/instructions/tool-usage.instructions.md` - Code conventions: `AGENTS.md`

{ "prompt": "---\ndescription: 'Initiates the new feature pipeline. The orchestrator classifies the feature, invokes workflow analysis, then coordinates the Plan→Implement→Review cycle via specialist agents.'\nargument-hint: \"Describe the new feature (e.g., 'Add a pricing section with 3 plans...')\"\nagent: 'orchestrator'\n---\n\n# Start Feature Pipeline\n\nThe orchestrator receives your feature request and orchestrates the complete development pipeline. See `.github/instructions/pipeline-workflow.instructions.md`.\n\n## Procedure\n\n### 1. Analyze (Engineer) Feature\n\nIf the user's description is incomplete, use `vscode_askQuestions` to clarify:\n\n```\n- header: \"Feature Scope\"\n question: \"What are the boundaries of this feature?\"\n- header: \"Acceptance Criteria\"\n question: \"How will we know the feature is ready?\"\n- header: \"Priority\"\n question: \"Does this feature replace something existing or is it entirely new?\"\n options:\n - label: \"Entirely new feature\"\n - label: \"Replaces/extends something existing\"\n - label: \"Variation of an existing component\"\n```\n\n### 2. Create Workflow Artifact + Issue\n\nCreate a GitHub issue in the project with:\n\n**Title:** `feat: [short feature description]`\n\n**Body:**\n\n```markdown\n### Motivation\n\n[Why is this feature needed? What problem does it solve?]\n\n### Description\n\n[What will be implemented, in detail]\n\n### Acceptance Criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n- [ ] Criterion 3\n\n### Reference Design\n\n[Links to inspirations, mockups, or similar components on the site]\n\n### Affected Components\n\n- [list of existing components that will be modified]\n```\n\n### 3. Hand Off to Orchestrator\n\n🛑 **STOP and wait.** Present the issue to the user and wait for explicit approval before proceeding.\n\nAfter approval, execute the complete pipeline:\n\n1. Create branch `feat/short-description` from `main`\n2. Invoke `planner` (subagent) to analyze the codebase and generate an implementation plan\n3. Invoke `implementer` (subagent) to build the feature\n4. Invoke `code-reviewer` (subagent) to validate\n5. If critical/major → re-plan (max. 3x)\n6. Commit with `feat:` + push\n7. Create PR with `Closes #N`\n8. HITL — wait for PR review\n\n---\n\n## Commit Template (Feature)\n\n```\nfeat(scope): add feature description\n\nBrief description of what was implemented.\nKey decisions and patterns used.\n\nCloses #N\n```\n\n---\n\n## References\n\n- Complete pipeline: `.github/instructions/pipeline-workflow.instructions.md`\n- Tool usage: `.github/instructions/tool-usage.instructions.md`\n- Code conventions: `AGENTS.md`", "variables": [], "notes": "--- description: 'Initiates the new feature pipeline. The orchestrator classifies the feature, invokes workflow analysis, then coordinates the Plan→Implement→Review cycle via specialist agents.' argument-hint: \"Describe the new feature (e.g., 'Add a pricing section with 3 plans...')\" agent: 'orchestrator' ---", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/zan-ia/zan-visual-novel", "path": ".github/prompts/start-feature.prompt.md", "ref": "13e46d90c517f4a0bc9716bcc63709b33bd03805", "url": "https://github.com/zan-ia/zan-visual-novel/blob/13e46d90c517f4a0bc9716bcc63709b33bd03805/.github/prompts/start-feature.prompt.md", "key": "zan-ia/zan-visual-novel/.github/prompts/start-feature.prompt.md" } } }

start-feature

About

Start Feature Pipeline

Procedure

1. Analyze (Engineer) Feature

2. Create Workflow Artifact + Issue

3. Hand Off to Orchestrator

Commit Template (Feature)

References

Use it

Manifest

Reviews