harness/.github/ISSUE_TEMPLATE/feature_request.yml
ythong c25e55b64b feat: harness + zio-harness Claude Code 플러그인 초기 배포
- harness: 도메인 한 줄 → 에이전트 팀 자동 생성 메타 스킬 (v1.2.0)
- zio-harness: React + Spring Boot + Mobile 풀스택 개발 에이전트 팀 (v1.0.0)
- 에이전트 4종: orchestrator / analyst / bot / agent
- PROJECT_MAP.md 폴더 구조 메모리 시스템
- references/: react, spring-boot, mobile, playwright, database, folder-map

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-17 13:48:56 +09:00

63 lines
1.9 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

name: Feature request
description: Propose a new capability or enhancement for Harness
title: "[feat] "
labels: ["enhancement", "needs-discussion"]
body:
- type: markdown
attributes:
value: |
Thanks for the idea. Features take a bit of back-and-forth — please help us with the "why" before the "what".
For anything RFC-sized (new pattern family, runtime support, breaking API), consider starting in [GitHub Discussions](https://github.com/revfactory/harness/discussions) first.
- type: textarea
id: problem
attributes:
label: What problem does this solve?
description: Describe the user or engineering pain point. Concrete scenario preferred.
placeholder: |
When I scaffold a team for ___, I end up manually ___ because ___.
validations:
required: true
- type: textarea
id: proposal
attributes:
label: Proposed solution
description: Your idea for fixing it. Sketch API / CLI / workflow if relevant.
validations:
required: true
- type: textarea
id: alternatives
attributes:
label: Alternatives considered
description: What other approaches did you think about, and why did you not pick them?
validations:
required: false
- type: dropdown
id: related-pattern
attributes:
label: Related team-architecture pattern (if any)
description: Which of the 6 built-in patterns is this most relevant to?
options:
- "Not pattern-specific"
- "Pipeline"
- "Fan-out / Fan-in"
- "Expert Pool"
- "ProducerReviewer"
- "Supervisor"
- "Hierarchical Delegation"
- "A new pattern (please describe below)"
validations:
required: true
- type: textarea
id: additional
attributes:
label: Additional context (optional)
description: Links, prior art, screenshots, anything else.
validations:
required: false