@jadeit/forge-ai 1.2.1 → 1.4.0

package/skills/forge-plan/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: forge-plan
+description: Forge AI Phase 1 - Planning and requirement analysis
+license: MIT
+compatibility: opencode
+---
+
+# Forge AI: Phase 1 - Planning
+
+Invoke the `@forge-plan` agent to begin Phase 1: Planning.
+
+## What Happens
+
+1. Context is loaded (existing README/brief if present)
+2. Planning agent creates required documents:
+   - `docs/planning/project-scope.md`
+   - `docs/planning/user-stories.md`
+   - `docs/planning/implementation-plan.md`
+   - `docs/planning/technology-and-architecture.md`
+3. Agent validates all required artifacts exist
+4. State is updated in `.forge/state.yaml`
+5. You confirm transition to Phase 2
+
+## Phase 1 Outputs
+
+| Document | Purpose |
+|----------|---------|
+| project-scope.md | Project aim, high-level design, technology choices |
+| user-stories.md | User stories that drive development |
+| implementation-plan.md | High-level phases to be implemented |
+| technology-and-architecture.md | Tech choices and architecture (C4 Model) |
+
+## Constraints
+
+- NO executable code, scaffolding, or infrastructure
+- Illustrative code snippets ARE permitted
+- Use Mermaid diagrams for architecture
+
+## Flags
+
+- `--only {artifact}` - Work on specific artifact only
+  - Options: project-scope, user-stories, implementation-plan, technology
+
+## Prerequisites
+
+None — Phase 1 is the starting point.
+
+## Next Steps
+
+After Phase 1 complete, use `/forge-design` for Phase 2: Design.

package/skills/forge-status/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: forge-status
+description: Forge AI - Diagnose and recover from state inconsistencies
+license: MIT
+compatibility: opencode
+---
+
+# Forge Status - State Recovery
+
+Diagnose and recover from Forge state inconsistencies.
+
+## What It Checks
+
+### 1. Phase Consistency
+- Verify `project_phase` matches phase_history
+- Check for orphaned phase entries
+- Validate phase transitions are logical
+
+### 2. Feature State Integrity
+- Validate all features have required fields
+- Check current_sub_phase is valid (1_discover through 8_summarise)
+- Verify task_document paths exist
+
+### 3. Task Document References
+- Verify all referenced task documents exist
+- Check for broken references
+- Validate frontmatter consistency
+
+### 4. Rework Tracking
+- Report rework loop counts
+- Warn if approaching thresholds
+
+### 5. Context Budget
+- Report context usage
+- Warn if approaching limits
+
+## Diagnostic Output Format
+
+```
+Forge Status Report
+====================
+
+Phase: 3 (Development)
+Active Features: 2
+  - auth-system: 5_implement (loops: 1/3)
+  - api-gateway: 3_clarify (loops: 0/3)
+
+Issues Found: 1
+  ⚠ WARN: docs/design/tasks/legacy-task.md references non-existent task
+```
+
+## Recovery Actions
+
+| Issue | Recovery |
+|-------|----------|
+| Missing phase history | Rebuild from artifacts |
+| Invalid sub-phase | Reset to valid state |
+| Broken task ref | Remove orphaned reference |
+| Corrupted state | Offer state reset |

package/skills/forge-test/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: forge-test
+description: Forge AI Phase 4 - Functional testing and UAT
+license: MIT
+compatibility: opencode
+---
+
+# Forge AI: Phase 4 - Testing
+
+Invoke the `@forge-test` agent to begin User Acceptance Testing.
+
+## What Happens
+
+1. User stories and acceptance criteria are loaded
+2. UAT checklist is presented
+3. For each item, you confirm: passed / failed / skipped
+4. Failed items → defect reports created in `docs/defects/`
+5. Results → `docs/testing/uat-results.md`
+6. State updated after your sign-off
+
+## UAT Gate Process
+
+1. Present checklist of user stories with acceptance criteria
+2. You verify each by running the project locally
+3. For each item: PASSED / FAILED / SKIPPED
+4. Failed items produce defect reports
+5. Skipped items logged with reason
+6. Phase 5 proceeds only after your sign-off
+
+## Requirements
+
+User acceptance testing MUST be done by:
+- Running the project locally
+- Validating each user story against implementation
+- NOT just running automated tests
+
+## Defect Handling
+
+For failed items:
+1. Create defect report in `docs/defects/`
+2. Document reproduction steps
+3. Classify: design or implementation
+4. Route to appropriate phase
+
+## Next Steps
+
+After Phase 4 complete, use `/forge-deploy` for Phase 5: Deployment.