requirement-detector

Detect writing specification requirements and load matching knowledge bases.

1|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/Lev0n82/TestDriverMCP --skill requirement-detector-lev0n82
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirement-detector
Source: https://github.com/Lev0n82/TestDriverMCP/tree/main/.agent/skills/quality-assurance/requirement-detector
Command: npx skills add https://github.com/Lev0n82/TestDriverMCP --skill requirement-detector-lev0n82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically detects writing norms and loads corresponding knowledge bases to guide style, pacing, and genre conventions.

Core Features & Use Cases

  • Norm detection: Recognizes style, pace, and genre keywords and loads relevant guidance.
  • Dynamic configuration: Writes configuration blocks to specification.md for consistent future writing.
  • Conflict resolution: Provides options when multiple norms conflict.

Quick Start

Tell the system you want fast-paced romantic fiction with anti-AI flavor; the detector loads fast-paced and romance knowledge and applies them during writing.

Frequently Asked Questions about requirement-detector

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

FAQPage Schema
How do I automatically detect writing style and genre requirements?

Requirement-detector recognizes style, pace, and genre keywords from your input and loads corresponding knowledge bases to guide your writing. Describe your writing constraints—such as fast-paced romantic fiction or anti-AI tone—and the Skill loads relevant norms for consistent application.

Can I resolve conflicts when multiple writing norms apply to the same task?

Yes. When style, pacing, and genre requirements conflict, requirement-detector identifies the competing norms and presents options to resolve them, helping you select or combine specifications that work together.

What does norm detection do for downstream writing workflows?

Norm detection loads writing specifications into configuration blocks that persist across future tasks. This satisfies functional requirements for automatic knowledge-base loading and configuration updates, enabling consistent guidance for downstream agent workflows.

How do I set up writing constraints automatically instead of manually configuring each task?

Requirement-detector writes configuration blocks to specification.md based on detected norms, eliminating manual setup. Once configured, these specifications apply consistently to future writing tasks without re-entry.

When should I use norm detection instead of manually selecting writing guidelines?

Use norm detection when you want to apply multiple style, pacing, or genre constraints simultaneously and need automatic compatibility validation. It saves time by eliminating manual guideline selection and detects conflicts before they affect your output.