OttoNet-Skills

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.

Execute exactly one explicitly requested and developer-approved step from an OttoNet HTML implementation plan in a .NET repository. Use only after plan approval and never advance to future steps automatically.

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.

Preserve and structure a complete BA or Team Leader task after project understanding and team patterns are documented. Use to create a task requirement report without inventing product or API behavior.

Investigate all direct and indirect .NET repository context for a documented BA task, including related entities, permissions, workflows, tests, and persistence. Use after task analysis and before requirement-gap resolution.

Learn evidence-backed .NET team implementation conventions from active code, Git history, and review evidence. Use after repository exploration and before reading a BA task or planning code changes.

Safely inspect the current Git workspace before any .NET company-task analysis or implementation. Use at the beginning of an OttoNet workflow and immediately before a requested implementation step to protect the developer's branch and local changes.