feature-census

Extract module capability inventories by merging code analysis, library enrichment, and Playwright runtime crawling.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/drshailesh88/build_playbook --skill feature-census
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-census
Source: https://github.com/drshailesh88/build_playbook/tree/main/skills/feature-census
Command: npx skills add https://github.com/drshailesh88/build_playbook --skill feature-census

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents missed test coverage and documentation gaps by creating a complete, evidence-based inventory of what a module can do and what the user can actually interact with.

Core Features & Use Cases

  • Complete capability extraction: Produces a feature inventory that merges code behavior, library-provided capabilities, and runtime-visible UI interactions.
  • Pre-test, pre-doc discovery: Use it before writing QA specs, E2E plans, or feature documentation to ensure nothing important is overlooked.
  • Post-build validation: Use it after building a feature to confirm what ended up working, what is dead/conditional, and what is emergent.

Quick Start

Run the /feature-census flow for the target module or route to generate a cross-referenced feature inventory for QA, specs, and documentation.

Frequently Asked Questions about feature-census

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

FAQPage Schema
How do I create a complete feature inventory before writing E2E tests?

Generate a feature inventory by merging deterministic code extraction, library capability enrichment, and Playwright runtime accessibility crawling to cross-reference every module interaction before QA planning.

What is feature census for QA planning?

Feature census is the process of discovering the complete capability surface of an application by cross-referencing static code analysis with empirical runtime crawling to prevent missed test coverage.

How do I validate runtime features after building a web module?

Validate runtime features by running a Playwright DOM crawl against the target route to confirm delivered behavior, identify conditional or dead interactions, and report cross-layer discrepancies without hallucinating features.

Does this feature discovery process detect library-provided capabilities automatically?

Yes, deterministic library capability enrichment detects registered library functions and merges them with source code extraction and runtime UI interactions to produce a cross-referenced feature inventory.

Can I use Playwright to crawl DOM accessibility for code analysis?

Yes, Playwright runtime accessibility and DOM crawling maps the empirical user interface interactions and merges them with static code analysis to identify emergent or conditional module capabilities.

What are the limitations of runtime crawling for feature extraction?

Runtime crawling cannot discover undocumented features or hidden code paths without UI triggers, relying entirely on source-import scoping and cross-layer discrepancy reporting to avoid hallucinating capabilities.