@cregis-dev/cckit 0.3.0 → 0.4.1

package/templates/bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-03-execute.md

@@ -1,111 +1,111 @@
----
-name: 'step-03-execute'
-description: 'Execute implementation - iterate through tasks, write code, run tests'
-
-nextStepFile: './step-04-self-check.md'
----
-
-# Step 3: Execute Implementation
-
-**Goal:** Implement all tasks, write tests, follow patterns, handle errors.
-
-**Critical:** Continue through ALL tasks without stopping for milestones.
-
----
-
-## AVAILABLE STATE
-
-From previous steps:
-
-- `{baseline_commit}` - Git HEAD at workflow start
-- `{execution_mode}` - "tech-spec" or "direct"
-- `{tech_spec_path}` - Tech-spec file (if Mode A)
-- `{project_context}` - Project patterns (if exists)
-
-From context:
-
-- Mode A: Tasks and AC extracted from tech-spec
-- Mode B: Tasks and AC from step-02 mental plan
-
----
-
-## EXECUTION LOOP
-
-For each task:
-
-### 1. Load Context
-
-- Read files relevant to this task
-- Review patterns from project-context or observed code
-- Understand dependencies
-
-### 2. Implement
-
-- Write code following existing patterns
-- Handle errors appropriately
-- Follow conventions observed in codebase
-- Add appropriate comments where non-obvious
-
-### 3. Test
-
-- Write tests if appropriate for the change
-- Run existing tests to catch regressions
-- Verify the specific AC for this task
-
-### 4. Mark Complete
-
-- Check off task: `- [x] Task N`
-- Continue to next task immediately
-
----
-
-## HALT CONDITIONS
-
-**HALT and request guidance if:**
-
-- 3 consecutive failures on same task
-- Tests fail and fix is not obvious
-- Blocking dependency discovered
-- Ambiguity that requires user decision
-
-**Do NOT halt for:**
-
-- Minor issues that can be noted and continued
-- Warnings that don't block functionality
-- Style preferences (follow existing patterns)
-
----
-
-## CONTINUOUS EXECUTION
-
-**Critical:** Do not stop between tasks for approval.
-
-- Execute all tasks in sequence
-- Only halt for blocking issues
-- Tests failing = fix before continuing
-- Track all completed work for self-check
-
----
-
-## NEXT STEP
-
-When ALL tasks are complete (or halted on blocker), read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-04-self-check.md`.
-
----
-
-## SUCCESS METRICS
-
-- All tasks attempted
-- Code follows existing patterns
-- Error handling appropriate
-- Tests written where appropriate
-- Tests passing
-- No unnecessary halts
-
-## FAILURE MODES
-
-- Stopping for approval between tasks
-- Ignoring existing patterns
-- Not running tests after changes
-- Giving up after first failure
-- Not following project-context rules (if exists)
+---
+name: 'step-03-execute'
+description: 'Execute implementation - iterate through tasks, write code, run tests'
+
+nextStepFile: './step-04-self-check.md'
+---
+
+# Step 3: Execute Implementation
+
+**Goal:** Implement all tasks, write tests, follow patterns, handle errors.
+
+**Critical:** Continue through ALL tasks without stopping for milestones.
+
+---
+
+## AVAILABLE STATE
+
+From previous steps:
+
+- `{baseline_commit}` - Git HEAD at workflow start
+- `{execution_mode}` - "tech-spec" or "direct"
+- `{tech_spec_path}` - Tech-spec file (if Mode A)
+- `{project_context}` - Project patterns (if exists)
+
+From context:
+
+- Mode A: Tasks and AC extracted from tech-spec
+- Mode B: Tasks and AC from step-02 mental plan
+
+---
+
+## EXECUTION LOOP
+
+For each task:
+
+### 1. Load Context
+
+- Read files relevant to this task
+- Review patterns from project-context or observed code
+- Understand dependencies
+
+### 2. Implement
+
+- Write code following existing patterns
+- Handle errors appropriately
+- Follow conventions observed in codebase
+- Add appropriate comments where non-obvious
+
+### 3. Test
+
+- Write tests if appropriate for the change
+- Run existing tests to catch regressions
+- Verify the specific AC for this task
+
+### 4. Mark Complete
+
+- Check off task: `- [x] Task N`
+- Continue to next task immediately
+
+---
+
+## HALT CONDITIONS
+
+**HALT and request guidance if:**
+
+- 3 consecutive failures on same task
+- Tests fail and fix is not obvious
+- Blocking dependency discovered
+- Ambiguity that requires user decision
+
+**Do NOT halt for:**
+
+- Minor issues that can be noted and continued
+- Warnings that don't block functionality
+- Style preferences (follow existing patterns)
+
+---
+
+## CONTINUOUS EXECUTION
+
+**Critical:** Do not stop between tasks for approval.
+
+- Execute all tasks in sequence
+- Only halt for blocking issues
+- Tests failing = fix before continuing
+- Track all completed work for self-check
+
+---
+
+## NEXT STEP
+
+When ALL tasks are complete (or halted on blocker), read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-04-self-check.md`.
+
+---
+
+## SUCCESS METRICS
+
+- All tasks attempted
+- Code follows existing patterns
+- Error handling appropriate
+- Tests written where appropriate
+- Tests passing
+- No unnecessary halts
+
+## FAILURE MODES
+
+- Stopping for approval between tasks
+- Ignoring existing patterns
+- Not running tests after changes
+- Giving up after first failure
+- Not following project-context rules (if exists)

package/templates/bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-04-self-check.md

@@ -1,111 +1,111 @@
----
-name: 'step-04-self-check'
-description: 'Self-audit implementation against tasks, tests, AC, and patterns'
-
-nextStepFile: './step-05-adversarial-review.md'
----
-
-# Step 4: Self-Check
-
-**Goal:** Audit completed work against tasks, tests, AC, and patterns before external review.
-
----
-
-## AVAILABLE STATE
-
-From previous steps:
-
-- `{baseline_commit}` - Git HEAD at workflow start
-- `{execution_mode}` - "tech-spec" or "direct"
-- `{tech_spec_path}` - Tech-spec file (if Mode A)
-- `{project_context}` - Project patterns (if exists)
-
----
-
-## SELF-CHECK AUDIT
-
-### 1. Tasks Complete
-
-Verify all tasks are marked complete:
-
-- [ ] All tasks from tech-spec or mental plan marked `[x]`
-- [ ] No tasks skipped without documented reason
-- [ ] Any blocked tasks have clear explanation
-
-### 2. Tests Passing
-
-Verify test status:
-
-- [ ] All existing tests still pass
-- [ ] New tests written for new functionality
-- [ ] No test warnings or skipped tests without reason
-
-### 3. Acceptance Criteria Satisfied
-
-For each AC:
-
-- [ ] AC is demonstrably met
-- [ ] Can explain how implementation satisfies AC
-- [ ] Edge cases considered
-
-### 4. Patterns Followed
-
-Verify code quality:
-
-- [ ] Follows existing code patterns in codebase
-- [ ] Follows project-context rules (if exists)
-- [ ] Error handling consistent with codebase
-- [ ] No obvious code smells introduced
-
----
-
-## UPDATE TECH-SPEC (Mode A only)
-
-If `{execution_mode}` is "tech-spec":
-
-1. Load `{tech_spec_path}`
-2. Mark all tasks as `[x]` complete
-3. Update status to "Implementation Complete"
-4. Save changes
-
----
-
-## IMPLEMENTATION SUMMARY
-
-Present summary to transition to review:
-
-```
-**Implementation Complete!**
-
-**Summary:** {what was implemented}
-**Files Modified:** {list of files}
-**Tests:** {test summary - passed/added/etc}
-**AC Status:** {all satisfied / issues noted}
-
-Proceeding to adversarial code review...
-```
-
----
-
-## NEXT STEP
-
-Proceed immediately to `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md`.
-
----
-
-## SUCCESS METRICS
-
-- All tasks verified complete
-- All tests passing
-- All AC satisfied
-- Patterns followed
-- Tech-spec updated (if Mode A)
-- Summary presented
-
-## FAILURE MODES
-
-- Claiming tasks complete when they're not
-- Not running tests before proceeding
-- Missing AC verification
-- Ignoring pattern violations
-- Not updating tech-spec status (Mode A)
+---
+name: 'step-04-self-check'
+description: 'Self-audit implementation against tasks, tests, AC, and patterns'
+
+nextStepFile: './step-05-adversarial-review.md'
+---
+
+# Step 4: Self-Check
+
+**Goal:** Audit completed work against tasks, tests, AC, and patterns before external review.
+
+---
+
+## AVAILABLE STATE
+
+From previous steps:
+
+- `{baseline_commit}` - Git HEAD at workflow start
+- `{execution_mode}` - "tech-spec" or "direct"
+- `{tech_spec_path}` - Tech-spec file (if Mode A)
+- `{project_context}` - Project patterns (if exists)
+
+---
+
+## SELF-CHECK AUDIT
+
+### 1. Tasks Complete
+
+Verify all tasks are marked complete:
+
+- [ ] All tasks from tech-spec or mental plan marked `[x]`
+- [ ] No tasks skipped without documented reason
+- [ ] Any blocked tasks have clear explanation
+
+### 2. Tests Passing
+
+Verify test status:
+
+- [ ] All existing tests still pass
+- [ ] New tests written for new functionality
+- [ ] No test warnings or skipped tests without reason
+
+### 3. Acceptance Criteria Satisfied
+
+For each AC:
+
+- [ ] AC is demonstrably met
+- [ ] Can explain how implementation satisfies AC
+- [ ] Edge cases considered
+
+### 4. Patterns Followed
+
+Verify code quality:
+
+- [ ] Follows existing code patterns in codebase
+- [ ] Follows project-context rules (if exists)
+- [ ] Error handling consistent with codebase
+- [ ] No obvious code smells introduced
+
+---
+
+## UPDATE TECH-SPEC (Mode A only)
+
+If `{execution_mode}` is "tech-spec":
+
+1. Load `{tech_spec_path}`
+2. Mark all tasks as `[x]` complete
+3. Update status to "Implementation Complete"
+4. Save changes
+
+---
+
+## IMPLEMENTATION SUMMARY
+
+Present summary to transition to review:
+
+```
+**Implementation Complete!**
+
+**Summary:** {what was implemented}
+**Files Modified:** {list of files}
+**Tests:** {test summary - passed/added/etc}
+**AC Status:** {all satisfied / issues noted}
+
+Proceeding to adversarial code review...
+```
+
+---
+
+## NEXT STEP
+
+Proceed immediately to `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md`.
+
+---
+
+## SUCCESS METRICS
+
+- All tasks verified complete
+- All tests passing
+- All AC satisfied
+- Patterns followed
+- Tech-spec updated (if Mode A)
+- Summary presented
+
+## FAILURE MODES
+
+- Claiming tasks complete when they're not
+- Not running tests before proceeding
+- Missing AC verification
+- Ignoring pattern violations
+- Not updating tech-spec status (Mode A)

package/templates/bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md

@@ -1,104 +1,104 @@
----
-name: 'step-05-adversarial-review'
-description: 'Construct diff and invoke adversarial review task'
-
-nextStepFile: './step-06-resolve-findings.md'
----
-
-# Step 5: Adversarial Code Review
-
-**Goal:** Construct diff of all changes, invoke adversarial review task, present findings.
-
----
-
-## AVAILABLE STATE
-
-From previous steps:
-
-- `{baseline_commit}` - Git HEAD at workflow start (CRITICAL for diff)
-- `{execution_mode}` - "tech-spec" or "direct"
-- `{tech_spec_path}` - Tech-spec file (if Mode A)
-
----
-
-### 1. Construct Diff
-
-Build complete diff of all changes since workflow started.
-
-### If `{baseline_commit}` is a Git commit hash:
-
-**Tracked File Changes:**
-
-```bash
-git diff {baseline_commit}
-```
-
-**New Untracked Files:**
-Only include untracked files that YOU created during this workflow (steps 2-4).
-Do not include pre-existing untracked files.
-For each new file created, include its full content as a "new file" addition.
-
-### If `{baseline_commit}` is "NO_GIT":
-
-Use best-effort diff construction:
-
-- List all files you modified during steps 2-4
-- For each file, show the changes you made (before/after if you recall, or just current state)
-- Include any new files you created with their full content
-- Note: This is less precise than Git diff but still enables meaningful review
-
-### Capture as {diff_output}
-
-Merge all changes into `{diff_output}`.
-
-**Note:** Do NOT `git add` anything - this is read-only inspection.
-
----
-
-### 2. Invoke Adversarial Review
-
-With `{diff_output}` constructed, load and follow the review task. If possible, use information asymmetry: load this step, and only it, in a separate subagent or process with read access to the project, but no context except the `{diff_output}`.
-
-```xml
-<invoke-task>Review {diff_output} using {project-root}/_bmad/core/tasks/review-adversarial-general.xml</invoke-task>
-```
-
-**Platform fallback:** If task invocation not available, load the task file and follow its instructions inline, passing `{diff_output}` as the content.
-
-The task should: review `{diff_output}` and return a list of findings.
-
----
-
-### 3. Process Findings
-
-Capture the findings from the task output.
-**If zero findings:** HALT - this is suspicious. Re-analyze or request user guidance.
-Evaluate severity (Critical, High, Medium, Low) and validity (real, noise, undecided).
-DO NOT exclude findings based on severity or validity unless explicitly asked to do so.
-Order findings by severity.
-Number the ordered findings (F1, F2, F3, etc.).
-If TodoWrite or similar tool is available, turn each finding into a TODO, include ID, severity, validity, and description in the TODO; otherwise present findings as a table with columns: ID, Severity, Validity, Description
-
----
-
-## NEXT STEP
-
-With findings in hand, read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-06-resolve-findings.md` for user to choose resolution approach.
-
----
-
-## SUCCESS METRICS
-
-- Diff constructed from baseline_commit
-- New files included in diff
-- Task invoked with diff as input
-- Findings received
-- Findings processed into TODOs or table and presented to user
-
-## FAILURE MODES
-
-- Missing baseline_commit (can't construct accurate diff)
-- Not including new untracked files in diff
-- Invoking task without providing diff input
-- Accepting zero findings without questioning
-- Presenting fewer findings than the review task returned without explicit instruction to do so
+---
+name: 'step-05-adversarial-review'
+description: 'Construct diff and invoke adversarial review task'
+
+nextStepFile: './step-06-resolve-findings.md'
+---
+
+# Step 5: Adversarial Code Review
+
+**Goal:** Construct diff of all changes, invoke adversarial review task, present findings.
+
+---
+
+## AVAILABLE STATE
+
+From previous steps:
+
+- `{baseline_commit}` - Git HEAD at workflow start (CRITICAL for diff)
+- `{execution_mode}` - "tech-spec" or "direct"
+- `{tech_spec_path}` - Tech-spec file (if Mode A)
+
+---
+
+### 1. Construct Diff
+
+Build complete diff of all changes since workflow started.
+
+### If `{baseline_commit}` is a Git commit hash:
+
+**Tracked File Changes:**
+
+```bash
+git diff {baseline_commit}
+```
+
+**New Untracked Files:**
+Only include untracked files that YOU created during this workflow (steps 2-4).
+Do not include pre-existing untracked files.
+For each new file created, include its full content as a "new file" addition.
+
+### If `{baseline_commit}` is "NO_GIT":
+
+Use best-effort diff construction:
+
+- List all files you modified during steps 2-4
+- For each file, show the changes you made (before/after if you recall, or just current state)
+- Include any new files you created with their full content
+- Note: This is less precise than Git diff but still enables meaningful review
+
+### Capture as {diff_output}
+
+Merge all changes into `{diff_output}`.
+
+**Note:** Do NOT `git add` anything - this is read-only inspection.
+
+---
+
+### 2. Invoke Adversarial Review
+
+With `{diff_output}` constructed, load and follow the review task. If possible, use information asymmetry: load this step, and only it, in a separate subagent or process with read access to the project, but no context except the `{diff_output}`.
+
+```xml
+<invoke-task>Review {diff_output} using {project-root}/_bmad/core/tasks/review-adversarial-general.xml</invoke-task>
+```
+
+**Platform fallback:** If task invocation not available, load the task file and follow its instructions inline, passing `{diff_output}` as the content.
+
+The task should: review `{diff_output}` and return a list of findings.
+
+---
+
+### 3. Process Findings
+
+Capture the findings from the task output.
+**If zero findings:** HALT - this is suspicious. Re-analyze or request user guidance.
+Evaluate severity (Critical, High, Medium, Low) and validity (real, noise, undecided).
+DO NOT exclude findings based on severity or validity unless explicitly asked to do so.
+Order findings by severity.
+Number the ordered findings (F1, F2, F3, etc.).
+If TodoWrite or similar tool is available, turn each finding into a TODO, include ID, severity, validity, and description in the TODO; otherwise present findings as a table with columns: ID, Severity, Validity, Description
+
+---
+
+## NEXT STEP
+
+With findings in hand, read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-06-resolve-findings.md` for user to choose resolution approach.
+
+---
+
+## SUCCESS METRICS
+
+- Diff constructed from baseline_commit
+- New files included in diff
+- Task invoked with diff as input
+- Findings received
+- Findings processed into TODOs or table and presented to user
+
+## FAILURE MODES
+
+- Missing baseline_commit (can't construct accurate diff)
+- Not including new untracked files in diff
+- Invoking task without providing diff input
+- Accepting zero findings without questioning
+- Presenting fewer findings than the review task returned without explicit instruction to do so