Follow-up: Document 7 stub instruction files from comprehensive remediation

[ashleyshaw]

Overview

Follow-up work from the comprehensive frontmatter remediation (PR #574). All frontmatter validation errors have been resolved (0 errors), but the following instruction files remain underdocumented stubs with only frontmatter and no actual content.

Identified Stub Instruction Files (7 total)

These files have valid frontmatter but need substantive documentation content:

1. instructions/copilot-operations.instructions.md

   • Title: "Copilot Operations"
   • Scope: Unified Copilot operating guide: behaviour guardrails and process logging

2. instructions/file-organisation.instructions.md

   • Title: "File Organisation"
   • Scope: File placement rules and directory structure conventions

3. instructions/multi-platform-skill-manifests.instructions.md

   • Title: "Multi-Platform Skill Manifests"
   • Scope: Cross-platform skill manifest specifications

4. instructions/self-explanatory-code-commenting.instructions.md

   • Title: "Self-Explanatory Code Commenting"
   • Scope: Code commenting and documentation standards

5. instructions/spec-driven-workflow.instructions.md

   • Title: "Spec-Driven Workflow"
   • Scope: Specification-first development workflow guide

6. instructions/task-implementation.instructions.md

   • Title: "Task Implementation"
   • Scope: Task implementation procedures and standards

7. instructions/wordpress-project-planning.instructions.md

   • Title: "WordPress Project Planning"
   • Scope: WordPress-specific project planning guidelines

Documentation Template

Each instruction file should follow the pattern established in instructions/instructions.instructions.md:

---
[frontmatter fields]
---

## Role Declaration

[Who should follow these instructions]

## Overview

[Purpose and scope]

## General Rules

[Key principles]

## Detailed Guidance

[Specific procedures and examples]

## Examples

[Concrete examples]

## Validation

[How to verify compliance]

## References

[Related documentation links]

Success Criteria

• All 7 instruction files have substantive content (minimum 100-200 lines each)
• Follow established instruction file pattern and format
• All frontmatter is valid and present
• All cross-references and links are valid
• Content is specific to the scope described in the title/description

Related Issue

Addresses remaining work from #573 (Comprehensive audit and remediation)
Completes work started in PR #574

Priority

Medium — These files establish important operational and development standards. Documentation helps maintain consistency across the organization.

[linear-code]

LS-777