メニュー
Manages epic and story lifecycle for the KB Agent project. Reads epic files, verifies acceptance criteria, updates story status, and checks Definition of Done. Use when completing stories, starting new work, or auditing epic status.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Structured first-pass debugging for test failures, runtime errors, and unexpected behavior. USE FOR: test failure, assertion error, ImportError, traceback, debug failing test, fix broken test, diagnose error, runtime exception, mock error, config error. DO NOT USE FOR: complex multi-system design issues (escalate to @planner for re-planning).
Create, update, refactor, explain, or review Microsoft Agent Framework solutions. Use when working with the KB Agent (src/agent/) or any Microsoft Agent Framework code.
Patterns for adding governance, safety, and trust controls to AI agent systems using Microsoft Foundry and Azure API Management (APIM) AI Gateway. Use when: - Adding rate limiting, content safety, or jailbreak detection to agent traffic - Configuring APIM policies for token limits, throttling, or semantic caching - Leveraging Foundry tracing, evaluations, and agent monitoring - Implementing department-scoped access via JWT claims - Deciding what to handle at the platform layer vs. thin application code
Validates service boundary compliance in the KB Agent project. Use when working on cross-service imports, restructuring modules, or reviewing code that crosses service boundaries.
Performs comprehensive preflight validation of Bicep deployments to Azure. Use when: - Before deploying infrastructure to Azure - Reviewing or preparing Bicep files - Previewing what changes a deployment will make (what-if) - Verifying permissions are sufficient for deployment - Before running `azd -C infra/azure up`, `azd -C infra/azure provision`, or `az deployment` commands
Reviews Bicep modules, azure.yaml, and infrastructure changes for the KB Agent project. Checks naming, RBAC, module wiring, and doc sync. Use when working on infra/ or reviewing infrastructure PRs.
| name | epic-workflow |
| description | Manages epic and story lifecycle for the KB Agent project. Reads epic files, verifies acceptance criteria, updates story status, and checks Definition of Done. Use when completing stories, starting new work, or auditing epic status. |
Manage the KB Agent epic/story tracking workflow. Epic docs in docs/epics/ are the source of truth for all story status.
Epics follow this structure:
# Epic NNN — <Title> [✅ when all stories done]
> **Status:** Draft | In Progress | Done
## Stories
### Story N — <Title> [✅ when done]
> **Status:** Not Started | In Progress | Done
#### Deliverables
- [x] Completed deliverable
- [ ] Incomplete deliverable
#### Implementation Scope
| File | Action | Description | Status |
|------|--------|-------------|--------|
| `path/to/file.py` | Create | Description | ✅ |
#### Definition of Done
- [x] Code complete
- [x] Unit tests passing
- [ ] Integration tests passing
make dev-test # current repo-wide test suite passes
make dev-test # current repo-wide test suite
cd src/agent && uv run pytest tests -o addopts= -m "not uitest"
cd src/web-app && uv run pytest tests -o addopts= -m "not uitest"
cd src/functions && uv run pytest tests -o addopts= -m "not uitest"
make dev-test # run against the deployed environment once env vars are configured
- [ ] → - [x]✅ to the Status columnStatus: In Progress → Status: Done