ll-scan-product

Scan a codebase to identify product-focused issues against a goals document.

7|2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-scan-product
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ll-scan-product
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/skills/ll-scan-product
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-scan-product

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the drift between high-level product goals and actual implementation by identifying discrepancies and missing features within the codebase.

Core Features & Use Cases

  • Goal-Driven Analysis: Scans the repository to ensure code structure reflects the defined product roadmap.
  • Issue Identification: Automatically flags technical debt or missing functionality that prevents the project from meeting its stated objectives.
  • Use Case: Use this skill during a sprint planning phase to verify that the current worktree contains all necessary components required by the project goals document.

Quick Start

Use the ll-scan-product skill to analyze the current repository against the goals document and report any missing product-focused issues.

Frequently Asked Questions about ll-scan-product

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

FAQPage Schema
How do I check if my codebase aligns with product goals?

To check codebase alignment with product goals, scan the repository against a defined goals document to identify missing features and discrepancies. This validates that technical implementation matches strategic product requirements.

What is codebase alignment analysis for software repositories?

Codebase alignment analysis is the process of scanning a software repository to identify product-focused issues and gaps relative to a defined goals document. It ensures technical implementation matches strategic product requirements during development.

How do I identify technical debt preventing my project from meeting product objectives?

To identify technical debt preventing project objectives, scan the codebase to automatically flag missing functionality and discrepancies relative to the product goals document. This highlights gaps between implementation and roadmap.

Can I verify my worktree contains all necessary components for sprint planning?

You can verify your worktree contains necessary components by scanning the current repository against the project goals document. This validates project state and flags missing product-focused issues before sprint execution.

When do I need to validate project state against product documentation?

Validate project state against product documentation during long-horizon development cycles to maintain consistency. Scanning identifies alignment gaps and missing features when drift occurs between strategic goals and technical implementation.

Does codebase alignment scanning work without external dependencies?

Codebase alignment scanning operates directly within the software repository context without external dependencies. It analyzes the worktree against the goals document to report missing product-focused issues.