cc-devflow 4.2.0 → 4.4.1

package/.claude/skills/utility/journey-checker/pressure-scenarios.md

@@ -1,164 +0,0 @@
-# Journey Coherence Checker - Pressure Scenarios
-
-## Purpose
-TDD RED Phase: Define scenarios to test agent behavior WITHOUT the skill.
-
----
-
-## Scenario 1: Dependency Not Satisfied
-
-**Setup**:
-- REQ-007 declares `dependencies: ["RM-006", "RM-007"]`
-- RM-006 (REQ-004) is `release_complete`
-- RM-007 (REQ-005) is `release_complete`
-- But REQ-005's actual output doesn't match what REQ-007 expects
-
-**Pressure**:
-```
-User: "REQ-007 开发完成了，请帮我检查一下"
-```
-
-**Expected Baseline Behavior (WITHOUT skill)**:
-- Agent only checks REQ-007's internal consistency
-- Agent doesn't verify RM-007's output matches REQ-007's input expectation
-- Agent says "PASS" even though there's a gap
-
-**Desired Behavior (WITH skill)**:
-- Agent reads REQ-007's `dependencies` field
-- Agent reads REQ-005's actual output (from TECH_DESIGN or contracts)
-- Agent compares expected vs actual
-- Agent reports mismatch if found
-
----
-
-## Scenario 2: Milestone Success Criteria Not Met
-
-**Setup**:
-- M4 Success Criteria: "All 4 platforms can execute core workflows"
-- REQ-004, REQ-005, REQ-006 are `release_complete`
-- But only 2 platforms actually work (Claude + Codex)
-
-**Pressure**:
-```
-User: "M4 完成了吗？"
-```
-
-**Expected Baseline Behavior (WITHOUT skill)**:
-- Agent checks individual REQ status
-- Agent sees all REQs are complete
-- Agent says "M4 完成了"
-
-**Desired Behavior (WITH skill)**:
-- Agent reads M4's Success Criteria from ROADMAP.md
-- Agent verifies each criterion against actual implementation
-- Agent reports "2/4 platforms working, M4 not complete"
-
----
-
-## Scenario 3: Cumulative Scope Reduction
-
-**Setup**:
-- ROADMAP M4 originally planned 7 deliverables (RM-007 to RM-013)
-- Each REQ's PRD "slightly simplified" the scope
-- Final implementation covers only 60% of original vision
-
-**Pressure**:
-```
-User: "M4 的所有需求都开发完了，可以发布了吗？"
-```
-
-**Expected Baseline Behavior (WITHOUT skill)**:
-- Agent checks each REQ's status
-- Agent sees all are `release_complete`
-- Agent says "可以发布"
-
-**Desired Behavior (WITH skill)**:
-- Agent compares ROADMAP deliverables vs actual PRD scope
-- Agent calculates coverage percentage
-- Agent reports "60% coverage, 40% scope reduction detected"
-
----
-
-## Scenario 4: Journey Gap (Missing Glue)
-
-**Setup**:
-- User journey: `/flow-init` → `/flow-prd` → `/flow-epic` → `/flow-dev` → `/flow-release`
-- REQ-005 implements `/flow-dev` improvements
-- REQ-006 implements compiler
-- But there's no REQ connecting them (the "glue" is missing)
-
-**Pressure**:
-```
-User: "从 /flow-init 到 /flow-release 的完整流程能跑通吗？"
-```
-
-**Expected Baseline Behavior (WITHOUT skill)**:
-- Agent checks individual command implementations
-- Agent doesn't test end-to-end flow
-- Agent says "应该可以"
-
-**Desired Behavior (WITH skill)**:
-- Agent identifies the user journey
-- Agent traces through each step
-- Agent finds the gap between REQ-005 and REQ-006
-- Agent reports "Gap found: no integration between X and Y"
-
----
-
-## Scenario 5: Orphan Requirement
-
-**Setup**:
-- REQ-008 exists but is not mapped to any ROADMAP item
-- REQ-008 is `release_complete`
-- But it doesn't contribute to any Milestone
-
-**Pressure**:
-```
-User: "所有需求都完成了，项目进度如何？"
-```
-
-**Expected Baseline Behavior (WITHOUT skill)**:
-- Agent counts completed REQs
-- Agent reports "X/Y REQs complete"
-- Agent doesn't notice REQ-008 is orphan
-
-**Desired Behavior (WITH skill)**:
-- Agent maps REQs to ROADMAP items
-- Agent identifies REQ-008 as orphan
-- Agent reports "REQ-008 not mapped to any Milestone"
-
----
-
-## Test Execution Plan
-
-### Phase 1: Baseline Testing (RED)
-1. Create mock REQ-007 with unmet dependency
-2. Ask agent to verify REQ-007
-3. Document agent's response verbatim
-4. Identify rationalizations used
-
-### Phase 2: Skill Writing (GREEN)
-1. Write skill addressing baseline failures
-2. Re-run scenarios
-3. Verify agent now catches issues
-
-### Phase 3: Refinement (REFACTOR)
-1. Find new rationalizations
-2. Add explicit counters
-3. Re-test until bulletproof
-
----
-
-## Key Rationalizations to Watch For
-
-| Potential Excuse | Counter |
-|------------------|---------|
-| "依赖已经标记完成了" | 完成 ≠ 满足。检查实际输出。 |
-| "每个需求都通过了验证" | 单需求验证 ≠ 全局一致性。 |
-| "ROADMAP 是规划，不是承诺" | Success Criteria 是承诺。 |
-| "这超出了我的检查范围" | 这正是你的检查范围。 |
-| "用户没有要求检查全局" | 全局检查是隐含要求。 |
-
----
-
-**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md

package/.claude/skills/utility/npm-release/SKILL.md

@@ -1,314 +0,0 @@
----
-name: npm-release
-description: Use when ready to publish a new version of cc-devflow npm package to npm registry
----
-
-# NPM Release Workflow
-
-## Overview
-
-Standardized release process for cc-devflow npm package ensuring consistent versioning, changelog maintenance, and safe publishing.
-
-**Core Principle**: Atomic release - all version markers (package.json, CHANGELOG.md, git tag) must stay in sync.
-
-## When to Use
-
-Use this skill when:
-- ✅ Ready to release a new version of cc-devflow
-- ✅ All changes committed and pushed
-- ✅ On main branch with clean working directory
-- ✅ Need to publish to npm registry
-
-Don't use when:
-- ❌ Working directory has uncommitted changes
-- ❌ Not on main branch
-- ❌ Pre-release/beta versions (needs adaptation)
-
-## Release Types
-
-Follow [Semantic Versioning](https://semver.org/):
-
-| Type | Version Change | When |
-|------|---------------|------|
-| **Patch** | 2.4.3 → 2.4.4 | Bug fixes, minor improvements |
-| **Minor** | 2.4.4 → 2.5.0 | New features, backward compatible |
-| **Major** | 2.5.0 → 3.0.0 | Breaking changes |
-
-## Complete Workflow
-
-### Phase 1: Pre-Release Checks
-
-```bash
-# 1. Verify git status
-git status
-# MUST show: "On branch main", "working tree clean"
-
-# 2. Check current version
-cat package.json | grep version
-# e.g., "version": "2.4.3"
-
-# 3. Review recent changes
-git log --oneline -10
-```
-
-**STOP if**:
-- Not on main branch
-- Uncommitted changes exist
-- Unpushed commits exist
-
-### Phase 2: Version Updates
-
-**Step 1: Update CHANGELOG.md**
-
-Add new version section at the top (after `---`):
-
-```markdown
-## [X.Y.Z] - YYYY-MM-DD
-
-### 🎯 Release Title
-
-Brief description of main changes.
-
-#### Changed / Added / Fixed
-- Bullet point 1
-- Bullet point 2
-
-#### Benefits
-- ✅ Benefit 1
-- ✅ Benefit 2
-```
-
-**Step 2: Update package.json**
-
-```bash
-# Manually edit or use npm version
-npm version patch --no-git-tag-version  # For patch release
-npm version minor --no-git-tag-version  # For minor release
-npm version major --no-git-tag-version  # For major release
-```
-
-Or edit directly:
-```json
-{
-  "version": "X.Y.Z"
-}
-```
-
-### Phase 3: Git Operations
-
-**Step 1: Create Release Commit**
-
-```bash
-git add CHANGELOG.md package.json
-
-git commit -m "$(cat <<'EOF'
-chore(release): bump version to X.Y.Z
-
-Release X.Y.Z - [Brief title]
-
-主要变更：
-- 变更点 1
-- 变更点 2
-
-Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
-EOF
-)"
-```
-
-**Step 2: Create Annotated Tag**
-
-```bash
-git tag -a vX.Y.Z -m "$(cat <<'EOF'
-Release vX.Y.Z - [Brief title]
-
-🎯 Main changes:
-- Change 1
-- Change 2
-
-Benefits:
-✅ Benefit 1
-✅ Benefit 2
-
-Full changelog: https://github.com/Dimon94/cc-devflow/blob/main/CHANGELOG.md
-EOF
-)"
-```
-
-**Step 3: Verify**
-
-```bash
-# Check commit
-git log --oneline -1
-
-# Check tag
-git tag -l "v2.4.*" | tail -3
-
-# Verify tag annotation
-git show vX.Y.Z
-```
-
-### Phase 4: Publish
-
-**Step 1: Push to GitHub**
-
-```bash
-# Push commits
-git push origin main
-
-# Push tags
-git push origin vX.Y.Z
-# Or push all tags: git push origin --tags
-```
-
-**Step 2: Create GitHub Release (Optional)**
-
-Via GitHub CLI:
-```bash
-gh release create vX.Y.Z \
-  --title "vX.Y.Z - [Title]" \
-  --notes-file <(sed -n '/## \[X.Y.Z\]/,/## \[/p' CHANGELOG.md | head -n -1)
-```
-
-Or manually at: https://github.com/Dimon94/cc-devflow/releases/new
-
-**Step 3: Publish to npm**
-
-```bash
-# Test publish first (dry-run)
-npm publish --dry-run
-
-# Actual publish
-npm publish
-
-# Verify publication
-npm view cc-devflow version
-```
-
-## Quick Reference
-
-| Step | Command | Purpose |
-|------|---------|---------|
-| Check status | `git status` | Verify clean state |
-| Check version | `grep version package.json` | Current version |
-| Bump version | Edit package.json | Update version number |
-| Update changelog | Edit CHANGELOG.md | Document changes |
-| Create commit | `git commit -m "chore(release): ..."` | Commit version bump |
-| Create tag | `git tag -a vX.Y.Z -m "..."` | Tag release |
-| Push commits | `git push origin main` | Push to GitHub |
-| Push tags | `git push origin vX.Y.Z` | Push tag to GitHub |
-| Publish npm | `npm publish` | Publish to registry |
-
-## Common Mistakes
-
-### ❌ Mistake 1: Forgetting to Update CHANGELOG.md
-
-**Problem**: Version bumped but no changelog entry
-
-**Fix**: Always update CHANGELOG.md BEFORE committing
-
-### ❌ Mistake 2: Inconsistent Version Numbers
-
-**Problem**: package.json shows 2.4.4 but CHANGELOG.md shows 2.4.3
-
-**Fix**: Double-check all version numbers match before committing
-
-### ❌ Mistake 3: Pushing Tag Before Commit
-
-**Problem**: Tag points to wrong commit
-
-**Fix**: Always commit first, then tag, then push both together
-
-### ❌ Mistake 4: Not Testing npm publish
-
-**Problem**: Published package is broken
-
-**Fix**: Run `npm publish --dry-run` first to catch issues
-
-### ❌ Mistake 5: Network Timeout During Push
-
-**Problem**: `Failed to connect to github.com port 443`
-
-**Fix**:
-```bash
-# Option 1: Retry after network stabilizes
-git push origin main
-git push origin vX.Y.Z
-
-# Option 2: Switch to SSH (if HTTPS blocked)
-git remote set-url origin git@github.com:Dimon94/cc-devflow.git
-git push origin main
-```
-
-## Network Troubleshooting
-
-If `git push` fails with timeout:
-
-1. **Check network connectivity**:
-   ```bash
-   curl -I https://github.com 2>&1 | head -5
-   ```
-
-2. **Try SSH instead of HTTPS**:
-   ```bash
-   git remote -v  # Check current remote URL
-   git remote set-url origin git@github.com:Dimon94/cc-devflow.git
-   ```
-
-3. **If SSH fails (publickey error)**:
-   - Check SSH key: `ssh -T git@github.com`
-   - Add SSH key to GitHub: https://github.com/settings/keys
-   - Or stay with HTTPS and retry later
-
-4. **Commits and tags are safe locally**:
-   - They won't be lost
-   - Push when network is available
-
-## Post-Release Verification
-
-After successful release:
-
-```bash
-# 1. Verify GitHub tag
-open https://github.com/Dimon94/cc-devflow/tags
-
-# 2. Verify npm package
-npm view cc-devflow version
-npm view cc-devflow time
-
-# 3. Test installation
-npm install -g cc-devflow@latest
-cc-devflow --version  # Should show new version
-```
-
-## Rollback (If Needed)
-
-If published version has critical bugs:
-
-```bash
-# 1. Unpublish from npm (within 72 hours)
-npm unpublish cc-devflow@X.Y.Z
-
-# 2. Delete git tag locally and remotely
-git tag -d vX.Y.Z
-git push origin :refs/tags/vX.Y.Z
-
-# 3. Revert commit
-git revert HEAD
-
-# 4. Fix bug and re-release with new patch version
-```
-
-**Note**: npm unpublish is only available within 72 hours of publication. After that, publish a new patch version instead.
-
-## Real-World Impact
-
-Following this workflow ensures:
-- ✅ **Consistency**: All version markers stay in sync
-- ✅ **Traceability**: Clear changelog and git history
-- ✅ **Safety**: Dry-run catches issues before publishing
-- ✅ **Recoverability**: Can rollback if needed
-- ✅ **Automation-ready**: Scriptable workflow for future CI/CD
-
----
-
-**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md

package/.claude/skills/utility/skill-creator/LICENSE.txt

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.