Files

GitHub Actions 698ad86d17 chore: structured autonomy commands for planning, generating, and implementing features

- Create sa-generate.md for generating implementation documentation from plans
- Create sa-implement.md for executing implementation plans step-by-step
- Create sa-plan.md for collaborating with users to design development plans
- Add security scan commands for CodeQL, Docker images, Go vulnerabilities, and GORM
- Implement SQL code review and optimization commands
- Add supply chain vulnerability remediation process
- Introduce backend and frontend test commands with coverage checks
- Update settings.json for command permissions
- Document governance, project overview, code quality rules, and critical architecture rules in CLAUDE.md
- Establish root cause analysis protocol and definition of done for development

2026-03-08 05:45:21 +00:00

1.5 KiB

Raw Blame History

Create GitHub Issues from Implementation Plan

Create GitHub Issues for the implementation plan at: $ARGUMENTS

Process

Analyse the plan file to identify all implementation phases
Check existing issues using gh issue list to avoid duplicates
Create one issue per phase using gh issue create
Use appropriate templates from .github/ISSUE_TEMPLATE/ (feature or general)

Requirements

One issue per implementation phase
Clear, structured titles and descriptions
Include only changes required by the plan
Verify against existing issues before creation

Issue Content Structure

Title: Phase name from the implementation plan (e.g., feat: Phase 1 - Backend API implementation)

Description:

## Overview
[Phase goal from implementation plan]

## Tasks
[Task list from the plan's phase table]

## Acceptance Criteria
[Success criteria / DoD for this phase]

## Dependencies
[Any issues that must be completed first]

## Related Plan
[Link to docs/plans/current_spec.md or specific plan file]

Labels: Use appropriate labels:

feature — new functionality
chore — tooling, CI, maintenance
bug — defect fixes
security — security-related changes
documentation — docs-only changes

Commands

# List existing issues to avoid duplicates
gh issue list --state open

# Create a new issue
gh issue create \
  --title "feat: Phase 1 - [Phase Name]" \
  --body "$(cat <<'EOF'
## Overview
...
EOF
)" \
  --label "feature"

# Link issues (add parent reference in body)

1.5 KiB Raw Blame History