@mark-gozner/aigile-method 0.4.5

package/core/tasks/standup-digest.md

@@ -0,0 +1,21 @@
+<!-- BMAD-style scrum digest -->
+
+# SM Task: Standup Digest
+
+Summarize team status and highlight risks, dependencies, and immediate next steps.
+
+## Process (Sequential)
+
+1. Collect Inputs
+	- Yesterday/Today/Blockers; PRs; incidents; CI status
+2. Summarize Status
+	- Per person or per workstream; note trends
+3. Risks and Dependencies
+	- Cross-team impacts; blockers with owners
+4. Next Steps
+	- Immediate actions; help requests; decisions needed
+
+## Outputs
+
+- Standup summary with risks and actions
+- Short list of asks and decisions for leads

package/core/tasks/sync-jira-backlog.md

@@ -0,0 +1,32 @@
+<!-- BMAD-style PM backlog curation with deterministic outputs -->
+
+# PM Task: Sync Jira Backlog
+
+Curate and align the Jira backlog with current priorities, readiness, and sprint plans.
+
+## Inputs
+
+```yaml
+optional:
+  - boards: ['TEAM']
+  - filters: ['project = TEAM AND status in (Backlog, Ready) ORDER BY priority DESC']
+```
+
+## Process (Sequential)
+
+1. Pull Prioritized Items
+	- Apply filters; confirm priority, labels, components
+2. Ensure Readiness
+	- Definition of Ready: clear objective, AC, links, estimate
+3. Sprint Planning
+	- Propose next-sprint candidates based on capacity
+4. Update Status
+	- Move items to appropriate columns (Backlog/Ready/Selected)
+5. Communicate Summary
+	- Share changes, blockers, and asks with PO/Team
+
+## Outputs
+
+- Backlog delta report: items added/updated/moved
+- List of Ready items and next-sprint candidates
+- Blockers with owners

package/core/tasks/test-design.md

@@ -0,0 +1,68 @@
+<!-- Based on BMAD test-design; simplified for AIgile -->
+
+# QA Task: Test Design
+
+Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
+
+## Inputs
+
+```yaml
+required:
+	- story_id: '{epic}.{story}' # e.g., "1.3"
+	- story_path: '{devStoryLocation}/{epic}.{story}.*.md' # From core-config.yaml
+optional:
+	- story_title: '{title}'
+	- story_slug: '{slug}'
+```
+
+## Process (Sequential)
+
+1. Analyze Story Requirements
+	 - Break down each acceptance criterion (AC) into testable behaviors
+	 - Identify error paths and boundary cases per AC
+2. Choose Test Levels
+	 - Unit: pure logic and deterministic behaviors
+	 - Integration: module/service interactions, DB/IO boundaries
+	 - E2E: core user journeys and compliance flows
+3. Assign Priorities (Risk-Based)
+	 - P0: security, payments, data loss, revenue-critical
+	 - P1: core flows used daily
+	 - P2: secondary flows/admin
+4. Design Scenarios
+	 - For each AC, produce 1+ scenarios with: ID, level, priority, description, justification
+	 - Ensure at least one negative case and one boundary case overall
+5. Validate Coverage
+	 - Every AC has coverage; no redundant testing across levels
+	 - Critical flows have multiple levels where helpful
+
+## Outputs
+
+### Output 1: Test Design Summary
+
+- Scenario table grouped by AC with level and priority
+- Recommended execution order (P0s first, then P1, etc.)
+- Gaps list (if any) and suggested remediation
+
+### Output 2: Gate YAML Block (for QA Gate)
+
+```yaml
+test_design:
+	scenarios_total: X
+	by_level:
+		unit: Y
+		integration: Z
+		e2e: W
+	by_priority:
+		p0: A
+		p1: B
+		p2: C
+	coverage_gaps: []
+```
+
+## Quality Checklist
+
+- [ ] Each AC has at least one scenario
+- [ ] Levels chosen match the risk and behavior
+- [ ] Includes at least one negative and one boundary case
+- [ ] No duplicated coverage across levels
+- [ ] IDs follow `{epic}.{story}-{LEVEL}-{SEQ}`

package/core/tasks/validate-next-story.md

@@ -0,0 +1,37 @@
+# validate-next-story
+
+```yaml
+id: validate-next-story
+role: dev
+whenToUse: Before picking up a new story; validate readiness and clarify unknowns.
+elicit: true
+outcome: Readiness decision + clarified scope + initial implementation outline
+```
+
+## Objective
+Assess whether the next candidate story is sufficiently refined to begin implementation.
+
+## Preconditions
+- A story reference (ID, URL, or pasted content) is available.
+
+## Steps
+1. Request story identifier or full content if not provided.
+2. Extract: Title, Business Goal, Acceptance Criteria, Constraints, Dependencies.
+3. Evaluate acceptance criteria quality (testability, completeness, ambiguity).
+4. Identify missing info (environments, data impacts, non-functionals, error paths).
+5. Ask clarifying questions (batch them) — wait for answers.
+6. Propose a thin-slice implementation strategy (ordered list of work slices).
+7. Recommend: READY or NEEDS-REFINEMENT with rationale.
+
+## Outputs
+- Structured assessment:
+  - Summary
+  - AC Review (Good / Needs Clarification)
+  - Open Questions
+  - Proposed Slices
+  - Recommendation
+
+## Guidance
+- Prefer crisp bullet lists over prose.
+- If AC ambiguous, do NOT recommend READY.
+- Keep proposed slices implementation-agnostic when possible.

package/core/tasks/verify-jira-story-e2e.md

@@ -0,0 +1,45 @@
+<!-- BMAD-informed end-to-end verification process; AIgile paths -->
+
+# QA Task: Verify Jira Story End-to-End
+
+Validate that a Jira story is implemented correctly with adequate tests and quality signals across functional and non-functional aspects.
+
+## Inputs
+
+```yaml
+required:
+  - urlOrId: 'ENG-123' | 'https://your.atlassian.net/browse/ENG-123'
+optional:
+  - story_path: '{devStoryLocation}/{epic}.{story}.*.md'
+```
+
+## Process (Sequential)
+
+1. Load Story Context
+	- Fetch issue; restate objective and AC in your own words
+	- Cross-check with local story file if available
+2. Map AC → Test Scenarios
+	- Positive, negative, and boundary per critical AC
+	- Identify NFR checks needed (security/perf/reliability/maintainability)
+3. Execute Evidence Gathering
+	- Run relevant tests (unit/integration/e2e)
+	- Review SonarQube hotspots and issues touching changed code
+	- Validate logs/telemetry if available
+4. Findings and Verdict
+	- Summarize PASS/CONCERNS/FAIL with evidence
+	- Provide prioritized fix list and owners
+5. Gate Integration (optional)
+	- If acting as gate, produce gate file and story update per QA Gate task
+
+## Outputs
+
+- E2E verification report: verdict, evidence, gaps, and recommended fixes
+- Optional: gate file under `docs/qa/gates` and story QA Results update
+
+## Checklist
+
+- [ ] Each AC validated (functional + edge cases)
+- [ ] Critical NFRs assessed for this change
+- [ ] SonarQube has no new high/critical findings
+- [ ] Logs/telemetry show expected signals
+- [ ] Clear next actions with owners