feature-validator — community feature-validator, XAI-Threat-Attribution-IDS, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for Development Agents requiring rigorous feature validation against business requirements documents like BRD, FRD, and PRD. Validate all features against 6 core business requirement documents (BRD, FRD, MRD, PRD, SRS, BUSINESS_MODEL). Use when implementing any new feature, user story, or capability. Enforces requirements t

Joseph-VJ Joseph-VJ
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
30
Canonical Locale
en
Detected Body Locale
en

Ideal for Development Agents requiring rigorous feature validation against business requirements documents like BRD, FRD, and PRD. Validate all features against 6 core business requirement documents (BRD, FRD, MRD, PRD, SRS, BUSINESS_MODEL). Use when implementing any new feature, user story, or capability. Enforces requirements t

Core Value

Empowers agents to ensure feature alignment with core business documents, providing validation against BRD, FRD, MRD, PRD, SRS, and other business specifications, utilizing markdown files for documentation.

Ideal Agent Persona

Ideal for Development Agents requiring rigorous feature validation against business requirements documents like BRD, FRD, and PRD.

↓ Capabilities Granted for feature-validator

Validating features against Business Requirements Documents (BRD)
Aligning product development with Functional Requirements Documents (FRD)
Ensuring market requirements compliance using Market Requirements Documents (MRD)

! Prerequisites & Limits

  • Requires access to core business documents (BRD, FRD, MRD, PRD, SRS)
  • Must have markdown file format support for documentation
  • Limited to features outlined in referenced business documents

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is feature-validator?

Ideal for Development Agents requiring rigorous feature validation against business requirements documents like BRD, FRD, and PRD. Validate all features against 6 core business requirement documents (BRD, FRD, MRD, PRD, SRS, BUSINESS_MODEL). Use when implementing any new feature, user story, or capability. Enforces requirements t

How do I install feature-validator?

Run the command: npx killer-skills add Joseph-VJ/XAI-Threat-Attribution-IDS. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for feature-validator?

Key use cases include: Validating features against Business Requirements Documents (BRD), Aligning product development with Functional Requirements Documents (FRD), Ensuring market requirements compliance using Market Requirements Documents (MRD).

Which IDEs are compatible with feature-validator?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for feature-validator?

Requires access to core business documents (BRD, FRD, MRD, PRD, SRS). Must have markdown file format support for documentation. Limited to features outlined in referenced business documents.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Joseph-VJ/XAI-Threat-Attribution-IDS. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use feature-validator immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

feature-validator

Install feature-validator, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Feature Alignment Validator

Purpose

Ensure all features align with documented business requirements

Reference Documents (MUST CHECK ALL)

Core Business Docs (6 Required):

  1. BRD - docs/business/brd.md - Business Requirements
  2. FRD - docs/business/FRD.md - Functional Requirements
  3. MRD - docs/business/mrd.md - Market Requirements
  4. PRD - docs/business/PRD.md - Product Requirements
  5. SRS - docs/business/srs.md - Software Specifications
  6. BUSINESS_MODEL - docs/business/BUSINESS_MODEL.md - Revenue model

Supporting Documentation:

  • docs/business/FREE_FOR_BUYERS.md - Free buyer philosophy
  • docs/technical/SELLER_LISTING_FLOW_ANALYSIS.md - Feature flows
  • docs/DOCUMENTATION_INDEX.md - Full doc inventory
  • docs/PROJECT_OVERVIEW.md - High-level summary

AI Workflow for New Features

🔴 STEP 0: VALIDATE USER REQUEST (MANDATORY)

  • Read user's exact words - What feature do they want?
  • Understand their intent - Why do they want this feature?
  • Check for business conflicts - Does this match FREE_FOR_BUYERS.md and BUSINESS_MODEL.md?
  • Identify pricing implications - Will this be free or paid?
  • Ask clarifying questions - If uncertain, ask BEFORE searching docs

  1. 📝 Feature Request Received

  2. 🔍 Search ALL 6 docs for matching requirement

  3. Decision Tree:

    Feature in docs?
├─ ✅ YES → Proceed with implementation
└─ ❌ NO → Follow "Undocumented Feature Protocol"

Undocumented Feature Protocol

When feature is NOT in any of the 6 docs:

  1. 🛑 PAUSE implementation
  2. 📋 INFORM user:
    • "This feature is not documented in BRD/FRD/MRD/PRD/SRS/BUSINESS_MODEL"
    • "Searched: [list what you searched for]"
    • "Results: Not found"
  3. 💡 SUGGEST next steps:
    • Option A: Add feature to appropriate doc first (recommend which doc)
    • Option B: Skip this feature (explain why it might not fit)
    • Option C: Proceed anyway (explain risks)
  4. ⏸️ WAIT for user decision
  5. ✅ Proceed only after user confirms

Validation Checklist

  • Feature exists in at least ONE of the 6 docs?
  • Implementation matches documented requirements?
  • No conflicting requirements across docs?
  • User stories/use cases covered?
  • Business logic aligns with BUSINESS_MODEL?
  • Technical specs match SRS?
  • Functional behavior matches FRD?

Core Business Logic (Always Validate Against)

From BUSINESS_MODEL.md:

  • ✅ FREE for Buyers - All customer features must be free
  • ✅ Paid for Sellers - Revenue comes from promoters/sellers only
  • ✅ Offline-First - Must work without internet
  • ✅ Dual-Mode - Support both SQLite (offline) and Supabase (online)
  • ✅ Lead Generation - Maximize seller leads, not buyer friction

Red Flags (Alert User Immediately)

  • 🚫 Feature charges buyers money
  • 🚫 Feature breaks offline mode
  • 🚫 Feature conflicts with "free for buyers" model
  • 🚫 Feature requires always-online connection
  • 🚫 Feature not in any of the 6 reference docs

Related Skills

Looking for an alternative to feature-validator or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer