This commit is contained in:
gnekt
2026-03-22 17:13:17 +01:00
commit 299df8b1c9
48 changed files with 12762 additions and 0 deletions

View File

@@ -0,0 +1,83 @@
name: Agent Proposal
description: Propose a new crew member (11th agent or beyond).
title: "[Agent] "
labels: ["agent-proposal"]
body:
- type: markdown
attributes:
value: |
Want to add a new agent to the crew? Fill out the sections below.
Check the [contributing guide](https://github.com/gnekt/My-Brain-Is-Full-Crew/blob/main/CONTRIBUTING.md#propose-a-new-crew-member) for details on agent design.
- type: input
id: name
attributes:
label: Agent name
description: A short, descriptive codename (lowercase, hyphens only).
placeholder: "e.g. habit-tracker"
validations:
required: true
- type: textarea
id: role
attributes:
label: Role
description: What problem does this agent solve? Why is it needed?
validations:
required: true
- type: textarea
id: triggers
attributes:
label: Trigger phrases
description: When should this agent activate? List natural phrases a user might say.
placeholder: |
- "track my habits"
- "did I do X today?"
- "streak report"
validations:
required: true
- type: textarea
id: tools
attributes:
label: Tool access
description: Which tools does the agent need?
placeholder: "Read, Write, Edit, Glob, Grep"
validations:
required: true
- type: textarea
id: vault-integration
attributes:
label: Vault integration
description: Which folders does it read from or write to? Does it create new folders?
validations:
required: true
- type: textarea
id: inter-agent
attributes:
label: Inter-agent communication
description: Which existing agents should it interact with? How?
placeholder: "Should notify the Architect when a new tracking area is needed."
- type: textarea
id: gap
attributes:
label: Why it matters
description: What gap in the current crew does this fill? Why can't an existing agent cover this?
validations:
required: true
- type: dropdown
id: priority
attributes:
label: Suggested routing priority
description: Where should this agent sit in the routing priority table?
options:
- "High (1-3) - should override most other agents"
- "Medium (4-7) - standard priority"
- "Low (8-10) - runs after most other agents"
validations:
required: true

90
.github/ISSUE_TEMPLATE/bug_report.yml vendored Normal file
View File

@@ -0,0 +1,90 @@
name: Bug Report
description: Something is broken or not working as expected.
title: "[Bug] "
labels: ["bug"]
body:
- type: markdown
attributes:
value: |
Sorry you hit a bug! Please give us enough detail to reproduce it.
- type: textarea
id: what-happened
attributes:
label: What happened?
description: A clear description of the bug.
placeholder: "I asked the Scribe to save a note, but it created the file in the wrong folder..."
validations:
required: true
- type: textarea
id: expected
attributes:
label: Expected behavior
description: What did you expect to happen instead?
validations:
required: true
- type: textarea
id: repro
attributes:
label: Steps to reproduce
description: Minimal steps to trigger the bug.
placeholder: |
1. Open Claude Code in the vault
2. Say "save this note about..."
3. Observe that...
validations:
required: true
- type: dropdown
id: agent
attributes:
label: Agent involved
description: Which agent was active when the bug occurred?
options:
- architect
- scribe
- sorter
- seeker
- connector
- librarian
- transcriber
- postman
- Routing / dispatcher (CLAUDE.md)
- Unknown / not sure
validations:
required: true
- type: dropdown
id: severity
attributes:
label: Severity
description: How bad is this?
options:
- "Low - minor inconvenience, easy workaround"
- "Medium - broken feature, workaround exists"
- "High - broken feature, no workaround"
- "Critical - data loss, vault corruption, or security issue"
validations:
required: true
- type: textarea
id: vault-structure
attributes:
label: Vault structure (if relevant)
description: A rough outline of your vault folder structure, if the bug is structure-related.
render: text
- type: textarea
id: logs
attributes:
label: Logs / error output
description: Paste any relevant error messages or Claude Code output.
render: text
- type: textarea
id: context
attributes:
label: Additional context
description: Screenshots, OS, Claude model used, anything else that might help.

5
.github/ISSUE_TEMPLATE/config.yml vendored Normal file
View File

@@ -0,0 +1,5 @@
blank_issues_enabled: false
contact_links:
- name: Contributing Guide
url: https://github.com/gnekt/My-Brain-Is-Full-Crew/blob/main/CONTRIBUTING.md
about: Read the contributing guide before opening an issue.

44
.github/ISSUE_TEMPLATE/discussion.yml vendored Normal file
View File

@@ -0,0 +1,44 @@
name: Discussion
description: Open-ended topic, idea, feedback, or RFC.
title: "[Discussion] "
labels: ["discussion"]
body:
- type: markdown
attributes:
value: |
This is for open-ended conversations about the project's direction, design decisions, or ideas that don't fit neatly into a feature request.
- type: textarea
id: topic
attributes:
label: Topic
description: What do you want to discuss?
validations:
required: true
- type: dropdown
id: category
attributes:
label: Category
description: What kind of discussion is this?
options:
- Design / architecture decision
- Agent behavior philosophy
- Workflow / UX feedback
- Community / contribution process
- Roadmap / future direction
- Other
validations:
required: true
- type: textarea
id: context
attributes:
label: Context and thoughts
description: Background, reasoning, trade-offs, examples, or anything that helps frame the discussion.
- type: textarea
id: questions
attributes:
label: Open questions
description: Specific questions you'd like the community to weigh in on.

View File

@@ -0,0 +1,61 @@
name: Feature Request
description: Suggest a new feature or improvement to an existing one.
title: "[Feature] "
labels: ["enhancement"]
body:
- type: markdown
attributes:
value: |
Thanks for suggesting a feature! Please fill out the sections below so we can evaluate it properly.
- type: textarea
id: problem
attributes:
label: Problem
description: What problem does this feature solve? What friction are you experiencing?
placeholder: "When I try to do X, I have to manually do Y, which is tedious because..."
validations:
required: true
- type: textarea
id: solution
attributes:
label: Proposed Solution
description: Describe what you'd like to happen instead.
placeholder: "It would be great if the agent could automatically..."
validations:
required: true
- type: dropdown
id: scope
attributes:
label: Scope
description: Which part of the project does this affect?
options:
- Specific agent (specify below)
- Routing / CLAUDE.md
- Installer / scripts
- Documentation
- References / shared docs
- Other
validations:
required: true
- type: input
id: agent
attributes:
label: Agent (if applicable)
description: Which agent is this about?
placeholder: "e.g. scribe, postman, librarian"
- type: textarea
id: alternatives
attributes:
label: Alternatives Considered
description: Any workarounds or alternative approaches you've thought about?
- type: textarea
id: context
attributes:
label: Additional Context
description: Screenshots, examples, links, or anything else that helps explain the request.

44
.github/ISSUE_TEMPLATE/question.yml vendored Normal file
View File

@@ -0,0 +1,44 @@
name: Question
description: Ask for help with setup, usage, or how something works.
title: "[Question] "
labels: ["question"]
body:
- type: markdown
attributes:
value: |
Have a question? We're happy to help. Please check the README and docs first.
- type: textarea
id: question
attributes:
label: Your question
description: What do you need help with?
validations:
required: true
- type: dropdown
id: topic
attributes:
label: Topic
description: What area does this relate to?
options:
- Installation / setup
- Agent behavior
- Vault structure
- MCP / Gmail / Calendar integration
- Plugin mode
- Other
validations:
required: true
- type: textarea
id: tried
attributes:
label: What I've tried
description: Any steps you've already taken to find the answer?
- type: textarea
id: context
attributes:
label: Additional context
description: Any relevant details (OS, vault setup, error messages, etc.)