project-closeout

Governs the formal end of a project: documentation audit, deliverables sign-off, knowledge transfer, operational handover, DORA final report, and lessons learned. Trigger when: a project is wrapping up, a system is being handed to a sustaining team, a contract engagement is ending, a major version is closed and moving to maintenance, or the team needs to verify readiness for handover. Also trigger for: "close out the project", "handover to ops", "final handover", "project done checklist", "project wrap-up", "lessons learned", "DORA final report", "is the project done", "hand off to sustaining team", "engagement wrap-up".

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "project-closeout" with this command: npx skills add s3nex-com/skillsmp-s3nex-com-s3nex-com-project-closeout

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

Security

security-audit-secure-sdlc

Activate when assessing security posture, performing threat modelling, reviewing secure coding practices, evaluating dependency hygiene, auditing secrets management, designing security gates for CI/CD pipelines, or mapping practices to compliance frameworks (NIST SSDF, OWASP, SOC 2). Use for security architecture reviews, STRIDE analysis, SAST/DAST/SCA tool selection, secure design principle enforcement, vulnerability triage, penetration test scoping, supply chain security, build integrity, and producing security findings reports. Covers both proactive design-time security and reactive incident-response readiness.

Repository SourceNeeds Review
-0s3nex-com
Security

ai-assisted-engineering

Activate when engineers want to use AI tools more effectively in daily work — coding, review, debugging, refactoring, test generation. Use when establishing team norms for AI tool use, reviewing AI-generated code for correctness and security, diagnosing why AI tool results are poor quality, or deciding which tasks belong to Claude vs Cursor/Copilot vs human. Applies to Claude Code, Cursor, GitHub Copilot, MCP integrations, and agentic coding workflows.

Repository SourceNeeds Review
-0s3nex-com
Security

code-implementer

Activate when the user wants to implement code from a design document, break a technical design into ordered implementation tasks, generate code phase by phase following the DESIGN.md, write code that satisfies BDD acceptance criteria, implement APIs to their OpenAPI/Protobuf specs, or drive implementation with inline security and quality checkpoints. Also trigger for: "implement this", "write the code", "build it", "start coding", "implement the design", "code the feature", "implement phase 1", "write the service", "generate the implementation", "build from the design doc", "implement the spec".

Repository SourceNeeds Review
-0s3nex-com
Security

devops-pipeline-governance

Activate when designing or reviewing CI/CD pipelines, evaluating pipeline security and integrity, defining deployment strategies, establishing environment promotion policies, setting up release automation, governing infrastructure-as-code practices, defining rollback procedures, or troubleshooting pipeline failures blocking a release. Use for pipeline architecture, build reproducibility, deployment safety, environment parity, and the controls that ensure only reviewed and tested code reaches production.

Repository SourceNeeds Review
-0s3nex-com
project-closeout | V50.AI