skills.rest
patrickrmoore
patrickrmooreCOMMUNITY
Explore all skills by this author →
GitHub

instructions-management

Document and enforce project principles governing SDD workflow decisions.

Updated Mar 22, 2026
Search Tags:#templates#versioning#documentation#compliance#governance#principles
One-click install
npx skills add https://github.com/patrickrmoore/sdd-test --skill instructions-management
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: instructions-management
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.github/skills/instructions-management
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill instructions-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-negotiable project instructions gate all downstream decisions in SDD workflows, serving as the highest authority for governance.

Core Features & Use Cases

  • Defines the non-negotiable project principles that govern plan, specification, and task templates.
  • Outlines the update process for governance changes, including loading the current instructions, collecting placeholder values, drafting updates, and validating consistency.
  • Propagates governance changes across related specifications and templates, and produces a sync impact report to ensure alignment.
  • Enables versioning and compliance tracking across documents to maintain a single source of truth.

Quick Start

Update the project instructions document to reflect the latest principles and governance changes.

Frequently Asked Questions about instructions-management

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

FAQPage Schema
How do I enforce non-negotiable project principles across downstream tasks?▼

To enforce non-negotiable project principles, you can document them as high-authority instructions that gate all downstream decisions in SDD workflows. This ensures specifications and tasks automatically comply with your core governance rules.

What is the best way to version governance changes across plan templates?▼

Versioning governance changes across plan templates requires consistently updating version numbers and LAST_AMENDED_DATE fields. This process tracks compliance and maintains a single source of truth across all related documentation.

How do I propagate governance updates to related specifications?▼

Propagating governance updates involves loading current instructions, drafting changes, and validating consistency across related specifications. This produces a sync impact report to ensure complete alignment across your documentation.

Can I use compliance tracking to maintain a single source of truth for documentation?▼

Yes, compliance tracking maintains a single source of truth by enabling versioning across documents. This ensures that validation steps verify consistent updates to references like LAST_AMENDED_DATE and version numbers.

Why does versioning matter for project instructions in SDD workflows?▼

Versioning matters for project instructions because they serve as the highest authority for governance in SDD workflows. Proper versioning ensures downstream decisions are gated by the most current non-negotiable principles.

Related Skills

Explore More Legal & Compliance Skills→
sirkirbysirkirby
62

constitution-governance

Enforce OAK constitution amendment workflows and validation via the oak CLI.

Community
Advanced
hairihouhairihou

npm-update-report

Generate npm package update reports with changelog research and impact assessment.

Community
Advanced
kimen-devkimen-dev

speckit-constitution

Synchronize constitution templates with dependent specification and task artifacts.

Official
Advanced
estaciolimaestaciolima

speckit-constitution

Synchronize governance principles and versioning across dependent project templates.

Community
Advanced