メニュー
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.
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 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.
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 | plan-format |
| description | 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. |
Stored at .memory_bank/features/<feature-name>/plan.md.
# Implementation Plan: <Feature Name>
## Overview
Brief summary of the implementation approach.
## Phases
| Phase | Name | Description | Est. Complexity |
|-------|------|-------------|-----------------|
| 1 | <Phase Name> | Brief description | Low/Medium/High |
| 2 | <Phase Name> | Brief description | Low/Medium/High |
| ... | ... | ... | ... |
## Phase Order Rationale
Why phases are ordered this way. Dependencies between phases.
## Shared Considerations
- Patterns to follow across all phases
- Naming conventions specific to this feature
- Shared utilities or base classes needed
## Definition of Done
- [ ] All phases complete
- [ ] All tests passing
- [ ] All code reviews approved
- [ ] All phase reviews complete
- [ ] Final spec review approved
Stored at .memory_bank/features/<feature-name>/phases/phase-N-<name>.md.
# Phase N: <Phase Name>
## Status
- **Status:** Not Started | In Progress | Implementation Complete | Testing | Review | Complete
- **Implementer Iterations:** 0
- **Review Iterations:** 0
## Objective
What this phase accomplishes.
## Prerequisites
- Dependencies on prior phases
- Required setup or configuration
## Tasks
### Task 1: <Task Name>
- [ ] Step 1.1: Description
- [ ] Step 1.2: Description
- [ ] Step 1.3: Description
### Task 2: <Task Name>
- [ ] Step 2.1: Description
- [ ] Step 2.2: Description
## Files to Create/Modify
| File | Action | Purpose |
|------|--------|---------|
| `path/to/file.cs` | Create | Description |
| `path/to/existing.cs` | Modify | Description |
## Acceptance Criteria (from Spec)
- [ ] AC reference: description
- [ ] AC reference: description
## Testing Notes
- Key scenarios to test in this phase
- Edge cases specific to this phase
## Implementation Log
| Date | Action | Details |
|------|--------|---------|