Skip to content

docs: strengthen epic and issue planning publication checks - #20

Merged
vitormattos merged 1 commit into
mainfrom
docs/harden-issue-epic-workflow
Oct 9, 2026
Merged

vitormattos merged 1 commit into
mainfrom
docs/harden-issue-epic-workflow

Conversation

@vitormattos

Copy link
Copy Markdown
Member

Summary

Tighten the existing create-issues-and-epics skill based on the LibreSign Unified Search epic publication and review.

  • Require a GitHub capability preflight before publication approval, including issue types, native hierarchy and ordering, blocked-by relations, and effort/priority/project fields.
  • Ask whether each proposed child is an independently verifiable deliverable instead of an acceptance criterion or internal refactor.
  • Distinguish good first issue suitability from immediate readiness, including appropriately documented blocked newcomer tasks.
  • Require reproducible fixtures and before/after methodology when drafting performance work.
  • Reconcile the final GitHub state against the approved hierarchy, sibling order, dependencies, metadata and deliberate blanks before declaring publication complete.

Scope

Documentation-only update to the skill entrypoint and two existing references. No workflow executables, repository issue data, or other skills are changed.

Verification

  • Confirmed the changes are limited to three skill Markdown files via the main...docs/harden-issue-epic-workflow comparison.
  • Confirmed one commit ahead of main and no divergence.
  • Git Signing MCP verified OpenPGP signature and author-matching DCO.
  • Checked the existing entrypoint/frontmatter and in-memory edit anchors before committing.

Motivation

Addresses the repeated administrative reconciliation required after publishing LibreSign/libresign#9065 and avoids turning its particular implementation choices into universal skill rules.

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
@vitormattos
vitormattos merged commit afbf7c4 into main Oct 9, 2026
2 checks passed
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.

1 participant