Menu
Review one completed .NET implementation-plan step for requirement compliance, project consistency, validation evidence, and scope control before the developer manually commits. Use immediately after a step executor report.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Coordinate OttoNet's gated .NET company-task workflow from workspace inspection through final delivery review while preserving developer control over clarification, plan approval, each implementation step, commits, and push.
Perform a full evidence-based final delivery review for a completed .NET company task after all approved steps are reviewed. Use before the developer manually pushes; this skill never pushes code.
Create a detailed, developer-approved, stepwise HTML implementation plan for a resolved .NET company task. Use only after requirement-gap analysis confirms that no blocking clarification remains.
Extract repository rules, architecture guidance, and operational instructions before reading a BA task or exploring .NET business implementation. Use after workspace inspection in an OttoNet company-task workflow.
Map the active .NET base code, its actual module responsibilities, and request execution flows after project documentation is understood. Use before analyzing a BA task to build evidence-based project understanding without assuming an architecture.
Compare a BA task with .NET repository rules, code, and team patterns to resolve technical conventions, expose business ambiguity, and create clarification questions before planning. Use after task-context investigation.
| name | dotnet-step-reviewer |
| description | Review one completed .NET implementation-plan step for requirement compliance, project consistency, validation evidence, and scope control before the developer manually commits. Use immediately after a step executor report. |
Provide a focused pre-commit review of exactly one completed plan step. Decide whether it is ready for the developer to commit without implementing future work.
Use after dotnet-step-executor finishes a requested step and before the developer decides whether to commit. Re-run after corrective changes to the same step.
git status and diff for the review boundary.AWAITING_REVIEW, the plan and requested step match the execution report, and no freshness or protection-boundary mismatch exists. Stop on an unsafe mismatch.AWAITING_COMMIT_DECISION or BLOCKED) with report evidence so it can be recorded. Do not make changes unless separately and explicitly asked to execute the same step again.Use this order for any interpretation: 1) resolved task requirements, 2) original task requirements, 3) repository instructions and documentation, 4) approved merge requests, 5) resolved review comments, 6) recent merged code, 7) repeated current project patterns, 8) similar implementations, 9) generic .NET practices. Generic practices never override explicit task or project rules.
Stop with Ready for commit: No when requirement coverage is incomplete, scope leaked, validation fails or is materially missing, a safety issue exists, or a blocking ambiguity remains. Stop at the developer commit gate even when the review passes.
Produce a Step Completion Report, using ../../templates/step-completion-report.md. Include step executed, changed files, requirements and evidence IDs covered, validation commands and results, build/test status, warnings, plan deviations, unresolved issues, Ready for commit: Yes/No, and a suggested commit message.
If ready, stop for the Developer Commit Gate. After the developer decides and any state change is inspected, the next explicitly requested plan step may go to dotnet-step-executor; do not advance automatically.