메뉴
Submit feedback, bug reports, and feature requests from heir projects to Master Alex via AI-Memory/feedback/
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/fabioc-aloha/Alex_Plug_In --skill heir-feedback명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | heir-feedback |
| description | Submit feedback, bug reports, and feature requests from heir projects to Master Alex via AI-Memory/feedback/ |
| tier | standard |
| applyTo | **/*feedback*,**/*bug*,**/*feature-request* |
Report bugs, share feedback, and request features from any heir project back to Master Alex.
Heirs use a shared feedback folder in AI-Memory to communicate issues, ideas, and bug reports to the Master Alex maintainer. This is the standard channel for heir-to-master communication about problems and improvements.
| Item | Value |
|---|---|
| Feedback folder | AI-Memory/feedback/ |
| File format | Markdown (.md) |
| Naming convention |
{YYYY-MM-DD}-{type}-{short-title}.md |
| Types | bug, feature, improvement, question |
| Access | OneDrive sync (all surfaces read/write) |
Feedback lives in the shared AI-Memory folder, accessible from all AI surfaces:
OneDrive/AI-Memory/
├── profile.md
├── notes.md
├── learning-goals.md
├── global-knowledge.md
└── feedback/ ← Heir feedback channel
├── 2026-04-11-bug-synapse-broken-link.md
├── 2026-04-11-feature-new-skill-request.md
└── 2026-04-12-improvement-meditation-flow.md
| Surface | Path |
|---|---|
| VS Code (Windows) | %OneDrive%/AI-Memory/feedback/ or %OneDriveConsumer%/AI-Memory/feedback/ |
| VS Code (macOS) | ~/Library/CloudStorage/OneDrive-*/AI-Memory/feedback/ or ~/OneDrive/AI-Memory/feedback/ |
| Local fallback | ~/.alex/AI-Memory/feedback/ |
| M365 Copilot | OneDrive > AI-Memory > feedback (via OneDriveAndSharePoint) |
---
type: bug | feature | improvement | question
severity: critical | high | medium | low
heir: {project-name}
date: {YYYY-MM-DD}
status: new
---
# {Short descriptive title}
## Description
{What happened, what you expected, or what you want}
## Steps to Reproduce (bugs)
1. {Step 1}
2. {Step 2}
3. {Step 3}
## Expected Behavior
{What should have happened}
## Actual Behavior
{What actually happened}
## Context
- **Heir project**: {project name}
- **Alex version**: {e.g., 7.6.0}
- **Affected files**: {skill, instruction, or prompt paths}
- **Platform**: {VS Code / M365 / Agent Builder}
## Suggested Fix (optional)
{If you have ideas on how to fix it}
| Type | When to Use | Example |
|---|---|---|
| bug | Something is broken or incorrect | Skill has wrong API pattern, synapse points to deleted file |
| feature | New capability needed | "Need a skill for Terraform modules" |
| improvement | Existing thing could be better | "meditation instructions could mention episodic cleanup" |
| question | Unclear documentation or behavior | "What's the difference between tier:standard and tier:advanced?" |
| Severity | Criteria |
|---|---|
| critical | Blocks work entirely, data loss risk, security issue |
| high | Major functionality broken, significant workaround needed |
| medium | Minor functionality issue, easy workaround exists |
| low | Cosmetic, documentation typo, nice-to-have |
Name it following the convention: {YYYY-MM-DD}-{type}-{short-title}.md
Examples:
2026-04-11-bug-code-review-skill-missing-security-checks.md2026-04-11-feature-terraform-module-skill.md2026-04-12-improvement-meditation-episodic-cleanup.mdUse the template above. Be specific:
.github/copilot-instructions.mdWhen reviewing feedback in Master Alex:
AI-Memory/feedback/ with status new.github/ architecturesync-architecture.cjsnew → investigating → fixed → deleted
After fixing the issue, delete the feedback file. The fix is documented in:
Keeping resolved feedback files creates clutter and risks re-processing the same issue.
| Trigger | Response |
|---|---|
| "report a bug" | Guide through bug report template |
| "submit feedback" | Guide through feedback file creation |
| "feature request" | Guide through feature request template |
| "check feedback" | List pending feedback files (Master only) |
| "heir issue" | Route to feedback creation |
Skill created: 2026-04-11 | Category: heir-management | Status: Active
Create and maintain ASCII visual dashboards for project tracking with parallel lane progress bars
Store and manage voice samples for TTS cloning — portable, version-controlled audio references
Clear documentation through visual excellence