ndf-policies

Enforce NDF plugin policies for branch protection, PR reviews, and documentation structure.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/takemi-ohama/ai-plugins --skill ndf-policies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ndf-policies
Source: https://github.com/takemi-ohama/ai-plugins/tree/main/plugins/ndf/skills/ndf-policies
Command: npx skills add https://github.com/takemi-ohama/ai-plugins --skill ndf-policies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines the basic governance policies for the NDF plugin, ensuring consistent responses, documentation, and commit messaging. The description field is injected into context so there is no need to reference the message body.

Core Features & Use Cases

  • Establishes rules for responses in Japanese, documentation, and commit messages.
  • Enforces main branch protection: direct push/merge to main is prohibited; feature branches + PRs are required.
  • Commit/push/PR merge require user confirmation, providing guardrails for changes.
  • Context management: Serena memory is not used; knowledge is organized in a three-layer structure (docs/, AGENTS.md, and skills/).
  • Complex tasks are delegated to ndf:director; specialized tasks to corresponding agents.
  • Knowledge is stored in docs/ and procedures in skills/ to prevent AGENTS.md from bloating.
  • When needed, several tasks stay within a structured governance framework.

Quick Start

Review AGENTS.md and docs/ to apply the policy when starting new tasks.

Frequently Asked Questions about ndf-policies

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

FAQPage Schema
How do I enforce branch protection and require pull request reviews for my repository?

You can enforce branch protection by defining policies that prohibit direct pushes to main, require feature branches, and mandate PR reviews before any merge. This ensures compliant development workflows and consistent safety guardrails.

What is the best way to manage project documentation and prevent AGENTS.md from bloating?

To prevent AGENTS.md from bloating, structure knowledge into a three-layer system: store general knowledge in docs/, procedures in skills/, and keep AGENTS.md concise. This maintains organized, accessible project documentation.

How do I automate policy enforcement for commit messages and documentation practices?

Automate policy enforcement by injecting rules directly into context, requiring frontmatter presence, and mandating user confirmation for commits, pushes, and PR merges. This applies governance to documentation and contribution workflows.

Can I delegate complex tasks to specific agents within a structured governance framework?

Yes, complex tasks can be delegated to a director agent, while specialized tasks route to corresponding agents. This structured delegation maintains consistency and safety across all contribution workflows and knowledge management.

Does this policy plugin require Serena memory for context management?

No, Serena memory is not used. Context management relies on a three-layer structure using docs/, AGENTS.md, and skills/ to organize knowledge and procedures, ensuring consistent responses without external memory dependencies.

How do I structure knowledge and procedures to maintain consistency in compliance workflows?

Structure knowledge by storing reference information in docs/ and operational procedures in skills/. This separation enforces compliant knowledge management, prevents file bloating, and maintains consistent contribution workflows.