sdd-preflight

Validate documentation, SRP adherence, planning artifacts, and incident logs before code implementation.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/jsalio/My-sdd-flow --skill sdd-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-preflight
Source: https://github.com/jsalio/My-sdd-flow/tree/main/sdd-preflight
Command: npx skills add https://github.com/jsalio/My-sdd-flow --skill sdd-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that all preconditions are met before any code is written, preventing technical debt and maintaining code quality throughout the SDD pipeline.

Core Features & Use Cases

  • Pre-Implementation Checks: Runs mandatory checks for documentation, SRP validation, complete specs, and active incident logs.
  • Blocking on Failures: Blocks code implementation if any checks fail, requiring user resolution or acceptance of technical debt.
  • Documentation of Technical Debt: Logs technical debt as incidents in docs/sdd-incident-log.md for future resolution.

Quick Start

Run the /sdd-preflight command to start the pre-implementation verification process.

Frequently Asked Questions about sdd-preflight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check pre-implementation compliance to prevent technical debt?

Pre-implementation compliance checking validates documentation, SRP adherence, planning artifacts, and incident logs before coding, blocking implementation on failures to prevent technical debt.

What is checked during pre-implementation validation in a code pipeline?

Pre-implementation validation checks documentation presence, SRP adherence, complete specs, and active incident logs to enforce pipeline standards and prevent technical debt.

How do I enforce SDD pipeline standards before writing code?

Enforce SDD pipeline standards by running pre-implementation verification that blocks code implementation on check failures, requiring resolution or technical debt acceptance.

What happens if a pre-implementation compliance check fails?

If a compliance check fails, the process blocks code implementation and requires you to resolve the issue or explicitly accept and log the technical debt as an incident.

How is technical debt documented when pre-implementation checks are bypassed?

Bypassed pre-implementation checks document technical debt by logging incidents in `docs/sdd-incident-log.md` for future resolution, ensuring technical debt is tracked.

Do I need complete planning artifacts before starting code implementation?

Yes, complete planning artifacts are required before code implementation. Pre-implementation compliance validation checks for their presence to ensure pipeline standards are met.