preflight-profile-setup

Files (1)

• SKILL.md

SKILL.md (first lines)

# preflight-profile-setup

Purpose: define the repository-specific preflight model with explicit user approval.

## Use When

- A project needs different preflight checks than the neutral core.
- The user wants stack-specific validation gates.
- Finalize and publish must be blocked by repository-specific rules.

## Questions To Resolve

1. Which stacks require preflight checks?
2. Which checks are blocking vs advisory?
3. Which checks run before tests, finalize, publish, or graph refresh?
4. Which checks belong in neutral `.github` and which belong in `.mastermind`?

## Deliverables

- A clear preflight profile per stack.
- A publish-readiness profile for subtree workflows.
- A list of missing checks that still need implementation.

## Complexity Thresholds

- agent.md green: <= 120 physical AND <= 75 logical.
- agent.md yellow: 121-160 physical OR 76-110 logical.
- agent.md red: > 160 physical OR > 110 logical.
- SKILL.md green: <= 180 physical AND <= 110 logical.
- SKILL.md yellow: 181-240 physical OR 111-160 logical.
- SKILL.md red: > 240 physical OR > 160 logical.

## Split Rules

- red: hard fail preflight for new and modified files without split.
- yellow: split plan is required at the next modification.
- legacy red: size must not increase; modification requires split or explicit justified exception.

## Guardrails

- Do not enable blocking checks without user confirmation.
- Do not place repository-specific checks in neutral `.github` unless they are truly reusable.

From ArkadiuszSieracki/mastermind-agentic-sdlc-vscode-copilot, Apache-2.0.

More from ArkadiuszSieracki/mastermind-agentic-sdlc-vscode-copilot