skills.rest
agilebydesign
agilebydesignOFFICIAL
Explore all skills by this author →
GitHub

execute-rules

Bundle rules from rules/*.md into SKILL.md and validate deliverables with scanners.

1|Updated Feb 26, 2026
Search Tags:#automation#workflow#validation#rules#scanners
One-click install
npx skills add https://github.com/agilebydesign/agilebydesign-skills --skill execute-rules
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute-rules
Source: https://github.com/agilebydesign/agilebydesign-skills/tree/main/skills/execute_using_rules
Command: npx skills add https://github.com/agilebydesign/agilebydesign-skills --skill execute-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires scanner_bases, frontmatter_tags, nltk, and includes scripts (resource) components.

What problem does it solve?

Organizations often struggle to keep agent work aligned with a defined rule set. This skill bundles rule prose from rules/*.md into a single SKILL.md and enforces that alignment by driving automated scanners before and after work, reducing drift and rework.

Core Features & Use Cases

  • Bundle rule prose from rules/*.md into the SKILL.md between the execute_rules markers, so agents see the consolidated rules in one place.
  • Run scanners to validate outputs against the bundled rules and generate a violations report for quick remediation.
  • Use the corrections log workflow to capture issues and guide fixes without editing rule sources until the final validation passes.

Quick Start

Bundle the rules into SKILL.md and run scanners against your workspace to validate the deliverable.

Frequently Asked Questions about execute-rules

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

FAQPage Schema
How do I enforce workflow validation rules on generated outputs?▼

You can validate outputs against defined constraints by bundling rule prose from a local rules/ directory into SKILL.md and running automated scanners to generate a violations report for quick remediation.

What is the best way to consolidate multiple Markdown rule files for automated scanning?▼

Consolidating Markdown rule files involves bundling them into an SKILL.md file so automated scanners can check deliverables against the unified constraint set and generate a violations report.

Do I need a specific directory structure to run rule validation scanners?▼

Yes, you need a local rules/ directory containing Markdown rule files, an SKILL.md file with a bundle section, and a scanners/ directory to drive automated checks and corrections workflows.

Can I fix validation violations without editing the original rule sources?▼

Yes, you can use a corrections log workflow to capture scanner violations and guide fixes without editing rule sources, iterating until the final validation passes.

Why do my automated scanners keep missing constraints defined in separate Markdown files?▼

Scanners miss constraints when rule prose remains scattered across separate files instead of being bundled into a single SKILL.md section, preventing the unified validation needed to catch all violations.

Does the rule bundling workflow support a pre-work rules gate?▼

Yes, the rule bundling workflow applies to skills that define a pre-work rules gate, ensuring outputs conform to defined constraints by running scanners before and after work to reduce drift.

Related Skills

Explore More Software Engineering Skills→
andersnygaardandersnygaard
5

rule-making-skill

Analyze a directory and generate .claude/rules/ markdown files for Claude Code.

Community
Intermediate
JaimeJunrJaimeJunr
2

run-tests

Execute unit and integration tests, analyze failures, and re-run to verify corrections.

Community
Advanced
ammonfifeammonfife

bigmac-policies

Create, track, and manage organizational policies with tags and date validity.

Community
Advanced
kk20300113-pngkk20300113-png

plankton-code-quality

Format and lint code on every file edit in Claude Code workflows.

Community
Advanced