sentinel-methodology

Enforce investigation journals, vault maintenance, and quality gates across debugging sessions.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/DigiStrique-Solutions/sentinel --skill sentinel-methodology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentinel-methodology
Source: https://github.com/DigiStrique-Solutions/sentinel/tree/main/skills/sentinel-methodology
Command: npx skills add https://github.com/DigiStrique-Solutions/sentinel --skill sentinel-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sentinel Methodology provides a structured, repeatable framework to prevent context pollution, maintain a living knowledge vault, ensure session continuity, and enforce gate-based verification across debugging, investigations, and multi-step tasks.

Core Features & Use Cases

  • Investigation Journal Protocol: creates and manages step-by-step problem narratives to capture hypotheses, experiments, and outcomes.
  • Self-Healing Vault Loop: maintains vault health by tracking gotchas, decisions, investigations, and completed work with staleness checks.
  • Session Continuity & Quality Gates: preserves context between sessions and validates changes via a seven-gate quality assurance workflow.
  • Vault Maintenance & Governance: ensures retroactive consistency, ADRs, and proper documentation of decisions and investigations.
  • Use Case: debugging a complex bug across multiple sessions, recovering a crashed session, or performing pre-merge quality verification.

Quick Start

Launch Sentinel Methodology at the start of a debugging session to enforce journals, vault hygiene, and gate-based verification.

Frequently Asked Questions about sentinel-methodology

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

FAQPage Schema
How do I maintain debugging context across multiple sessions?

Maintain debugging context across multiple sessions by enforcing session continuity protocols that preserve problem narratives, hypotheses, and investigation outcomes between active work periods.

What is a knowledge vault in software development governance?

A knowledge vault in software development governance is a living repository that tracks decisions, gotchas, and completed work, maintained through staleness checks and retroactive consistency loops.

How do I enforce quality gates before a code commit?

Enforce pre-commit quality gates by applying a seven-gate verification workflow that validates changes, checks vault hygiene, and ensures traceable progress before merging code.

How do I document a complex bug investigation step by step?

Document a complex bug investigation step by step using an investigation journal protocol that captures problem narratives, hypotheses, experiments, and outcomes in structured templates.

Can I recover context after a crashed debugging session?

Recover context after a crashed debugging session by applying a self-healing vault loop that restores investigation journals and session continuity through structured procedural rules.

When do I need architecture decision records for debugging?

You need architecture decision records for debugging when explicit governance requires documenting decisions, investigations, and retroactive consistency to ensure repeatable outcomes across recovery scenarios.