Skip to content

fix(process): enforce plan approval before implementation#370

Merged
martincjarvis merged 1 commit intomainfrom
fix/292-plan-approval-enforcement
Jan 15, 2026
Merged

fix(process): enforce plan approval before implementation#370
martincjarvis merged 1 commit intomainfrom
fix/292-plan-approval-enforcement

Conversation

@martincjarvis
Copy link
Collaborator

Summary

  • Add DangerJS Rule 9 to warn when linked issues lack plan comments or approval
  • Update issue templates with Plan Approval section
  • Create general-issue.md template for non-skill work items
  • Update issue-driven-delivery skill with Automated Enforcement section
  • Add Plan Approval Workflow section to CONTRIBUTING.md
  • Document Issue Import skills from testing-strategy-skills-v2 collection #177 as workflow exemplar

Closes #292

Test plan


For Reviewers

Reviewed files: dangerfile.js, .github/ISSUE_TEMPLATE/skill-spec.md, .github/ISSUE_TEMPLATE/general-issue.md, skills/issue-driven-delivery/SKILL.md, CONTRIBUTING.md

Key verification points:

  • DangerJS Rule 9 correctly identifies plan comments using isPlanComment() function
  • Approval detection uses isApprovalComment() function with multiple patterns
  • Issue templates have consistent Plan Approval section format
  • Exemplar reference to Issue Import skills from testing-strategy-skills-v2 collection #177 is consistent across all updated files

🤖 Generated with Claude Code

Add automated enforcement for plan approval workflow:
- DangerJS Rule 9: warns when linked issue lacks plan comment or approval
- Updated skill-spec.md issue template with Plan Approval section
- Created general-issue.md template with Plan Approval section
- Updated issue-driven-delivery skill with Automated Enforcement section
- Added Plan Approval Workflow section to CONTRIBUTING.md
- Referenced Issue #177 as workflow exemplar

Refs: #292

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@martincjarvis martincjarvis enabled auto-merge (squash) January 15, 2026 15:58
@github-actions
Copy link

Messages
📖 All PR validation checks passed.

Generated by 🚫 dangerJS against 6a75ade

Copy link
Owner

@mcj-coder mcj-coder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed dangerfile.js, CONTRIBUTING.md, skill-spec.md, general-issue.md, and issue-driven-delivery SKILL.md.

Verification:

  • isPlanComment() function correctly identifies plan comments by header, docs/plans link, or approval language
  • isApprovalComment() function detects multiple approval patterns
  • Rule 9 uses warn() not fail() which is appropriate for initial rollout
  • Issue templates have consistent Plan Approval section format
  • CONTRIBUTING.md Plan Approval Workflow section matches skill documentation
  • Issue #177 exemplar reference is consistent across all files

No concerns found. Logic is correct and non-breaking. Approved.

@martincjarvis martincjarvis merged commit 8d89a4d into main Jan 15, 2026
6 checks passed
@mcj-coder mcj-coder deleted the fix/292-plan-approval-enforcement branch January 15, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(process): Require plan approval comments on issues before implementation

2 participants