lev-align

Audit codebase alignment against north star documentation and classify drift types.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/lev-os/lev-content --skill lev-align
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lev-align
Source: https://github.com/lev-os/lev-content/tree/main/sources/skills/lev-align
Command: npx skills add https://github.com/lev-os/lev-content --skill lev-align

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill audits the alignment between a product's current development state and its stated strategic direction (north star), identifying and proposing corrections for drift.

Core Features & Use Cases

  • North Star Auditing: Compares codebase activity, documentation, and decisions against the defined north star.
  • Drift Detection: Identifies various types of misalignment, including stale documentation, product pivots, and coverage gaps.
  • Correction Proposals: Suggests specific actions to update documentation, adjust the north star, or realign development efforts.
  • Use Case: Run an audit before a major release to confirm that all ongoing work directly supports the product's core vision and priorities.

Quick Start

Run a full alignment audit for the lev project.

Frequently Asked Questions about lev-align

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

FAQPage Schema
How do I detect product strategy drift in my codebase?

North star alignment auditing compares your codebase state, canonical documentation, and issue tracking data against defined product strategy. It identifies and classifies misalignments such as stale documentation, product pivots, and coverage gaps to confirm development supports your core vision.

What is the best way to audit codebase alignment before a major release?

Running a full alignment audit before a major release confirms ongoing work directly supports your product vision. It compares codebase activity against canonical documentation and issue tracking systems to detect coverage gaps and propose actionable corrections.

Do I need issue tracking systems access to perform a north star audit?

Yes, north star auditing requires access to issue tracking systems alongside current codebase state and canonical documentation. This access enables accurate comparison of development activity and decisions against your stated product strategy.

How do I fix stale documentation and coverage gaps found during an audit?

Correction proposals suggest specific actions to update stale documentation, adjust the north star, or realign development efforts. These actionable corrections directly address the drift types identified during the codebase and product strategy audit.