requirement-detector_skill

Overview

This skill detects a user's writing requirement keywords and automatically loads the matching requirement document into the session. It activates when users mention terms like AI flavor, de-AI, natural, fast-paced, sweet, angst, no-toxic-points, serious literature, or strong emotion, and helps enforce the selected constraints during writing.

How this skill works

The skill scans user input for a curated keyword list and maps matches to predefined requirement profiles (e.g., anti-ai-v4, fast-paced, no-poison). Once a profile is suggested, it can display the requirement summary, load the full knowledge base into context, and write configuration markers into the project spec so future writing tasks follow those rules. When multiple profiles are detected, the skill checks compatibility and proposes merges or conflict resolutions.

When to use it

• When you want to remove or reduce AI-generated phrasing from prose (de-AI).
• When planning a fast-paced or '爽文' narrative that needs chapter-level hooks.
• When you need to ensure logical consistency and avoid 'toxic' plot devices.
• When writing emotionally intense or cathartic scenes and need rhythm control.
• When producing romance that must be strictly HE (sweet) or BE/angst (hurt).

Best practices

• Confirm the detected requirement before applying it to avoid unwanted constraints.
• Combine compatible profiles (e.g., natural-voice + fast-paced) and review suggested trade-offs.
• Use the loaded requirement summaries to set clear chapter-level goals (pacing, emotion beats).
• Adjust requirements mid-project based on reader feedback; the skill supports iterative updates.
• When conflicts arise, prefer explicit resolution suggestions from the skill rather than silent merging.

Example use cases

• User says 'make it less AI-sounding' → suggest anti-ai-v4 and offer to load that guide.
• User requests 'fast-paced, lots of hits per chapter' → attach fast-paced rules and pacing checklist.
• Writer building a romance: 'I want high sugar, HE' → apply romance-sweet and block BE elements.
• Draft has logic holes → apply no-poison profile to flag and remove downgraded-intelligence beats.
• Planning a tragic arc: 'I need controlled angst, not melodrama' → apply romance-angst with degree limits.