/f5-strict

description: Strict Implementation Protocol (SIP)
argument-hint: <start|approve|mark|validate>

/f5-strict - Strict Implementation Protocol Command

Enforce strict implementation of ONLY specified requirements with full traceability tracking.

ARGUMENTS

The user's request is: $ARGUMENTS

PURPOSE

Strict Implementation Protocol (SIP) ensures:

• Only specified requirements are implemented
• Full traceability from requirement to code
• No feature creep or scope expansion
• Coverage tracking and compliance reporting

WORKFLOW OVERVIEW

STRICT IMPLEMENTATION PROTOCOL
════════════════════════════════════════════════════════════════

  1. START SESSION
     └── Load requirements file
     └── Parse requirements list
     └── Generate checklist
             ↓
  2. PREFLIGHT APPROVAL
     └── Review checklist
     └── Confirm: "Implement ONLY these items"
     └── Lock scope
             ↓
  3. IMPLEMENTATION
     └── Mark items: pending → in_progress → done
     └── Add traceability comments in code
     └── Track coverage
             ↓
  4. VALIDATION
     └── Scan code for traceability comments
     └── Match with requirements
     └── Report coverage %
             ↓
  5. END SESSION
     └── Final validation
     └── Generate compliance report
     └── Archive session

════════════════════════════════════════════════════════════════

STEP 1: PARSE SUBCOMMAND

| Pattern | Action | |---------|--------| | `start <file>` | **START_SESSION** | | `check` | **CHECK_STATUS** | | `approve` | **APPROVE_PREFLIGHT** | | `checklist` | **SHOW_CHECKLIST** | | `mark <REQ-ID> <status>` | **MARK_STATUS** | | `validate` | **VALIDATE_IMPL** | | `report` | **GENERATE_REPORT** | | `status` | **SHOW_SESSION** | | `end` | **END_SESSION** | | `pause` | **PAUSE_SESSION** | | `resume` | **RESUME_SESSION** | | (default) | **SHOW_HELP** |

---

ACTION: START_SESSION

`/f5-strict start <requirements.md>`

Start a strict implementation session.

WORKFLOW:

1. Load requirements file
2. Parse requirements (REQ-XXX, FR-XXX, NFR-XXX, UC-XXX, US-XXX, SPEC-XXX)
3. Categorize by priority
4. Generate preflight checklist
5. Create session file: .f5/strict-session.json
6. Wait for approval

Output

## Strict Implementation Protocol

**Loading:** {{REQUIREMENTS_FILE}}

### Requirements Found

| Priority | Count |
|----------|-------|
| Critical | {{CRITICAL_COUNT}} |
| High | {{HIGH_COUNT}} |
| Medium | {{MEDIUM_COUNT}} |
| Low | {{LOW_COUNT}} |
| **Total** | **{{TOTAL_COUNT}}** |

════════════════════════════════════════════════════════════════
                    PREFLIGHT CHECKLIST
════════════════════════════════════════════════════════════════

You are about to implement ONLY:

### [Critical]
{{#each CRITICAL}}
○ {{this.id}}: {{this.description}}
{{/each}}

### [High]
{{#each HIGH}}
○ {{this.id}}: {{this.description}}
{{/each}}

### [Medium]
{{#each MEDIUM}}
○ {{this.id}}: {{this.description}}
{{/each}}

### [Low]
{{#each LOW}}
○ {{this.id}}: {{this.description}}
{{/each}}

════════════════════════════════════════════════════════════════

### SCOPE LOCK WARNING

Any feature NOT in this list is OUT OF SCOPE.

If you discover new requirements during implementation:
1. Document them separately
2. Do NOT implement them in this session
3. Add to backlog for future planning

### Next Step

Run `/f5-strict approve` to confirm and lock scope.

---

ACTION: CHECK_STATUS

`/f5-strict check`

Quick check before implementation (used by CLAUDE.md).

WORKFLOW:

1. Check if .f5/strict-session.json exists
2. Return session status
3. Indicate if implementation is allowed

Output

## Strict Mode Check

{{#if NO_SESSION}}
### Status: NO_SESSION

No active strict implementation session.

To start a session:

/f5-strict start <requirements.md> /f5-strict approve

{{/if}}

{{#if PENDING_APPROVAL}}
### Status: PENDING_APPROVAL

Session exists but not yet approved.

Run `/f5-strict approve` to confirm scope.
{{/if}}

{{#if PAUSED}}
### Status: PAUSED

Session is paused.

Run `/f5-strict resume` to continue.
{{/if}}

{{#if ACTIVE}}
### Status: ACTIVE

Session: {{SESSION_ID}}
Progress: {{DONE}}/{{TOTAL}} ({{PERCENTAGE}}%)

Ready to implement.

Quick Check:
```json
{
  "canImplement": true,
  "blockers": []
}

{{/if}}

---

## ACTION: APPROVE_PREFLIGHT

### `/f5-strict approve`

Approve the preflight checklist and lock scope.

```markdown
## Preflight Approval

### Confirming Scope Lock

You are agreeing to:
1. Implement ONLY the {{TOTAL_COUNT}} requirements listed
2. NOT add any features outside this list
3. Add traceability comments in code
4. Run validation before ending session

### Approved

Session ID: {{SESSION_ID}}
Status: ACTIVE
Scope: LOCKED

### Implementation Guidelines

1. **Mark progress** as you implement:

/f5-strict mark REQ-001 in_progress /f5-strict mark REQ-001 done src/auth/service.ts:10-50

2. **Add traceability comments** in code:
   ```typescript
   // REQ-001: User authentication with JWT
   export class AuthService {
     // ...
   }

3. **Validate** periodically:

   /f5-strict validate

4. **End session** when done:

   /f5-strict end

Ready to Implement

---

## ACTION: SHOW_CHECKLIST

### `/f5-strict checklist`

Display implementation checklist with progress.

### Options

| Option | Description |
|--------|-------------|
| `--pending` | Show only pending items |
| `--done` | Show only completed items |
| `--in-progress` | Show only in-progress items |
| `--blocked` | Show only blocked items |
| `--critical` | Show only critical priority |
| `--all` | Show all items (default) |

### Output

```markdown
## Implementation Checklist

**Session:** {{SESSION_ID}}
**Status:** {{STATUS}}

### Progress

[{{PROGRESS_BAR}}] {{PERCENTAGE}}%

| Status | Count |
|--------|-------|
| ✅ Done | {{DONE_COUNT}} |
| 🔄 In Progress | {{IN_PROGRESS_COUNT}} |
| ⬜ Pending | {{PEND