菜单
Defines the due diligence findings document format and analysis process for C# features. Use when performing due diligence analysis, documenting findings, or reviewing integration points and risks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Defines C# code review standards, review checklist, and review document format. Use when reviewing code, documenting review findings, or understanding code quality expectations.
General C# and .NET coding conventions, patterns, and best practices. Use when implementing, reviewing, or planning C# code. Covers naming, architecture, patterns, and common practices.
Defines the implementation plan and individual phase document formats for C# feature development. Use when creating plans, breaking work into phases, or defining task checklists.
Defines the complete C# SDLC workflow process including phase ordering, decision points, loop conditions, and artifact locations. Use when orchestrating feature development, understanding the workflow sequence, or determining which phase comes next.
Defines the C# feature specification document format and template. Use when writing, updating, or reviewing a feature spec. Includes sections for requirements, acceptance criteria, constraints, and dependencies.
Defines SQA testing standards, MSTest patterns, test writing guidelines, and test results documentation format for C# projects. Use when writing tests, documenting test results, or reviewing test quality.
| name | due-diligence-format |
| description | Defines the due diligence findings document format and analysis process for C# features. Use when performing due diligence analysis, documenting findings, or reviewing integration points and risks. |
Findings are stored at .memory_bank/features/<feature-name>/findings.md.
# Due Diligence Findings: <Feature Name>
## Date
<date>
## Codebase Analysis
### Affected Files & Modules
| File/Module | Impact | Notes |
|-------------|--------|-------|
| `path/to/file.cs` | Modified | Description of changes needed |
### Existing Patterns Identified
- Pattern 1: How it's currently done, how to follow it
- Pattern 2: ...
### Integration Points
- Service/module 1: How this feature connects
- Service/module 2: ...
## Risk Assessment
### High Risk
- **Risk:** Description
- **Impact:** What happens if this goes wrong
- **Mitigation:** How to address it
### Medium Risk
- ...
### Low Risk
- ...
## Dependency Analysis
### NuGet Packages
| Package | Current Version | Action Needed |
|---------|----------------|---------------|
| Package.Name | x.y.z | Add / Update / None |
### External Services
- Service name: dependency description
## Spec Gaps Found
- [ ] Gap 1: Description — resolution/recommendation
- [ ] Gap 2: ...
## Assumptions
- Assumption 1: Documentation of what was assumed
- ...
## Recommendations
1. Recommendation with rationale
2. ...
## Spec Updates Made
- List of changes made to spec.md as a result of this analysis