@jadeit/forge-ai 0.0.0 → 1.4.0

package/skills/forge-template-loader/SKILL.md

@@ -0,0 +1,162 @@
+---
+name: forge-template-loader
+description: Load and apply Forge document templates for all phases and artifacts
+license: MIT
+compatibility: opencode
+metadata:
+  audience: forge-users
+  workflow: document-creation
+---
+
+# Forge Template Loader
+
+Load and apply Forge document templates for all phases and artifacts.
+
+## Template Locations
+
+```
+.forge/templates/
+├── planning/
+│   ├── project-scope.md
+│   ├── user-stories.md
+│   ├── implementation-plan.md
+│   └── technology-and-architecture.md
+├── design/
+│   ├── design-decisions.md
+│   ├── task-list.md
+│   └── tasks/
+│       └── TASK_TEMPLATE.md
+├── testing/
+│   └── uat-results.md
+└── defects/
+    └── DEFECT_TEMPLATE.md
+```
+
+## Usage by Phase
+
+### Phase 1: Planning Templates
+
+Load from `.forge/templates/planning/`:
+
+| Document | Template | Output Location |
+|----------|----------|-----------------|
+| Project Scope | `project-scope.md` | `docs/planning/project-scope.md` |
+| User Stories | `user-stories.md` | `docs/planning/user-stories.md` |
+| Implementation Plan | `implementation-plan.md` | `docs/planning/implementation-plan.md` |
+| Technology & Architecture | `technology-and-architecture.md` | `docs/planning/technology-and-architecture.md` |
+
+### Phase 2: Design Templates
+
+Load from `.forge/templates/design/`:
+
+| Document | Template | Output Location |
+|----------|----------|-----------------|
+| Design Decisions | `design-decisions.md` | `docs/design/design-decisions.md` |
+| Task List | `task-list.md` | `docs/design/task-list.md` |
+| Individual Task | `tasks/TASK_TEMPLATE.md` | `docs/design/tasks/{task-slug}.md` |
+
+### Phase 4: Testing Templates
+
+| Document | Template | Output Location |
+|----------|----------|-----------------|
+| UAT Results | `testing/uat-results.md` | `docs/testing/uat-results.md` |
+
+### Defect Templates
+
+| Document | Template | Output Location |
+|----------|----------|-----------------|
+| Defect Report | `defects/DEFECT_TEMPLATE.md` | `docs/defects/{defect-slug}.md` |
+
+## Template Variables
+
+When applying templates, replace these placeholders:
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `[Task Title]` | Title of the task | "Implement user authentication" |
+| `[Task Slug]` | URL-safe identifier | "implement-user-auth" |
+| `[YYYY-MM-DD]` | Date placeholder | "2026-03-22" |
+| `[timestamp]` | ISO 8601 timestamp | "2026-03-22T10:00:00Z" |
+| `[Persona]` | User persona name | "End User" |
+| `[Goal]` | User goal | "reset my password" |
+| `[Benefit]` | User benefit | " regain access to my account" |
+
+## Required Frontmatter Fields
+
+### Task Document
+
+```yaml
+---
+title: [Task Title]
+status: not-started
+mode: greenfield | brownfield
+complexity: small | medium | large
+categories:
+  - backend
+affected_modules: []
+dependencies: []
+---
+```
+
+### Defect Document
+
+```yaml
+---
+title: [Defect Title]
+severity: critical | high | medium | low
+classification: design | implementation
+status: open
+source:
+  type: sentry | logs | test | uat | user-report
+  url: null
+  discovered: [timestamp]
+affected_features: []
+routed_to: null
+---
+```
+
+## Template Application Process
+
+### Creating a New Document
+
+1. **Read the template** from `.forge/templates/`
+2. **Replace placeholders** with actual values
+3. **Set initial status** in frontmatter (e.g., `status: in-progress`)
+4. **Set dates** to current timestamp
+5. **Write to destination** in `docs/`
+
+### Example: Creating a Task Document
+
+```
+Input: TASK_TEMPLATE.md
+Variables:
+  title = "Implement user authentication"
+  slug = "implement-user-auth"
+  complexity = "medium"
+  categories = ["backend", "database"]
+
+Output: docs/design/tasks/implement-user-auth.md
+```
+
+## Template Validation
+
+After creating a document, validate:
+
+1. **Frontmatter present** - Document starts with `---`
+2. **Required fields** - All required fields populated
+3. **Valid enums** - Status, mode, complexity use valid values
+4. **File path** - Correct location and naming
+
+## Modifying Templates
+
+Templates can be customized per project:
+
+1. Copy from `.forge/templates/` to project root
+2. Modify as needed
+3. Use project-local template instead of global
+
+Or extend `.forge/config.yaml`:
+```yaml
+templates:
+  custom_path: .forge/templates-custom/
+```

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.

package/templates/defects/DEFECT_TEMPLATE.md

@@ -0,0 +1,96 @@
+---
+title: [Defect Title]
+severity: critical
+classification: implementation
+status: open
+source:
+  type: sentry
+  url: null
+  discovered: null
+affected_features: []
+routed_to: null
+reproduction_steps: []
+expected_behaviour: null
+actual_behaviour: null
+created: null
+last_updated: null
+---
+
+# Defect Report: [Title]
+
+## Summary
+
+<!-- One-line summary of the defect -->
+
+## Severity
+
+- [ ] Critical - System unusable, data loss risk
+- [ ] High - Major feature broken, no workaround
+- [ ] Medium - Feature broken, workaround exists
+- [ ] Low - Minor issue, cosmetic
+
+## Classification
+
+- **Design** - Flawed design that needs revisiting
+- **Implementation** - Incorrect implementation of correct design
+
+## Source
+
+| Field | Value |
+|-------|-------|
+| Type | sentry / logs / test / uat / user-report |
+| URL | |
+| Discovered | |
+
+## Affected Features
+
+- 
+
+## Reproduction Steps
+
+1. 
+2. 
+3. 
+
+## Expected Behaviour
+
+<!-- What should happen -->
+
+## Actual Behaviour
+
+<!-- What actually happens -->
+
+## Screenshots / Logs
+
+<!-- Include relevant screenshots or log excerpts -->
+
+## Environment
+
+| Field | Value |
+|-------|-------|
+| Browser/OS | |
+| Version | |
+| User Type | |
+
+## Resolution
+
+### Routed To
+
+- Design phase (`forge 2:design`)
+- Build phase (`forge 3:build`)
+
+### Root Cause
+
+<!-- Analysis of the root cause -->
+
+### Fix Applied
+
+<!-- How the defect was resolved -->
+
+### Resolution Date
+
+## Changelog
+
+| Date | Action | By |
+|------|--------|-----|
+|      |        |     |

package/templates/design/design-decisions.md

@@ -0,0 +1,64 @@
+---
+title: Design Decisions
+phase: 2
+status: in-progress
+created: null
+last_updated: null
+---
+
+# Design Decisions
+
+## Decision Record Template
+
+| Field | Value |
+|-------|-------|
+| **Decision ID** | ADDR-001 |
+| **Date** | YYYY-MM-DD |
+| **Status** | Proposed / Accepted / Deprecated |
+| **Deciders** | |
+| **Context** | |
+| **Decision** | |
+| **Consequences** | |
+
+---
+
+## ADDR-001: [Title]
+
+**Status:** Accepted
+
+### Context
+
+<!-- What is the issue or decision being addressed? -->
+
+### Decision
+
+<!-- What is the change that is proposed or has been made? -->
+
+### Alternatives Considered
+
+1. **Option A:** 
+   - Pros: 
+   - Cons: 
+
+2. **Option B:** 
+   - Pros: 
+   - Cons: 
+
+### Consequences
+
+**Positive:**
+- 
+
+**Negative:**
+- 
+
+**Neutral:**
+- 
+
+---
+
+## Decision Index
+
+| ID | Title | Status | Date |
+|----|-------|--------|------|
+| ADDR-001 |        |        |      |

package/templates/design/task-list.md

@@ -0,0 +1,56 @@
+---
+title: Task List
+phase: 2
+status: in-progress
+created: null
+last_updated: null
+---
+
+# Task List
+
+## Summary
+
+| Total Tasks | Small | Medium | Large |
+|-------------|-------|--------|-------|
+|             |       |        |       |
+
+## Tasks by Category
+
+### Backend
+| Task Slug | Title | Complexity | Dependencies |
+|-----------|-------|------------|--------------|
+|           |       |            |              |
+
+### Frontend
+| Task Slug | Title | Complexity | Dependencies |
+|-----------|-------|------------|--------------|
+|           |       |            |              |
+
+### Infrastructure
+| Task Slug | Title | Complexity | Dependencies |
+|-----------|-------|------------|--------------|
+|           |       |            |              |
+
+### Database
+| Task Slug | Title | Complexity | Dependencies |
+|-----------|-------|------------|--------------|
+|           |       |            |              |
+
+### Documentation
+| Task Slug | Title | Complexity | Dependencies |
+|-----------|-------|------------|--------------|
+|           |       |            |              |
+
+## Task Dependencies Graph
+
+```mermaid
+flowchart LR
+    A[Task A] --> B[Task B]
+    B --> C[Task C]
+```
+
+## Implementation Order Recommendation
+
+1. 
+2. 
+3. 

package/templates/design/tasks/TASK_TEMPLATE.md

@@ -0,0 +1,87 @@
+---
+title: [Task Title]
+status: not-started
+mode: greenfield
+complexity: medium
+categories:
+  - backend
+affected_modules: []
+dependencies: []
+acceptance_criteria: []
+created: null
+last_updated: null
+---
+
+# Task: [Title]
+
+## Summary / Objective
+
+<!-- What this task achieves and why it is needed -->
+
+## User Story Reference
+
+<!-- Link to the user story this task supports: US-XXX -->
+
+## Acceptance Criteria
+
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Criterion 3
+
+## Implementation Detail
+
+### Approach
+
+<!-- How to implement this task -->
+
+### Components to Create/Modify
+
+| Component | Action | Description |
+|-----------|--------|-------------|
+|           |        |             |
+
+### Illustrative Code
+
+```typescript
+// Example interface or pseudo-code
+interface Example {
+  id: string;
+  // ...
+}
+```
+
+### API Changes
+
+| Endpoint | Method | Description |
+|----------|--------|-------------|
+|          |        |             |
+
+## Testing Criteria
+
+### Unit Tests
+
+- Test case 1
+- Test case 2
+
+### Integration Tests
+
+- Integration scenario 1
+
+### Manual Tests
+
+- Manual verification step 1
+
+## Edge Cases
+
+- Edge case 1 and how it is handled
+- Edge case 2 and how it is handled
+
+## Notes
+
+<!-- Additional context, concerns, or decisions -->
+
+## Changelog
+
+| Date | Change | By |
+|------|--------|-----|
+|      |        |     |

package/templates/planning/implementation-plan.md

@@ -0,0 +1,59 @@
+---
+title: Implementation Plan
+phase: 1
+status: in-progress
+created: null
+last_updated: null
+phases: []
+timeline_estimate: null
+---
+
+# Implementation Plan
+
+## Overview
+
+<!-- Brief description of the implementation approach -->
+
+## Phase Breakdown
+
+| Phase | Description | Estimated Duration | Dependencies |
+|-------|-------------|-------------------|--------------|
+| 1     | Planning    |                   | -            |
+| 2     | Design      |                   | Phase 1      |
+| 3     | Build       |                   | Phase 2      |
+| 4     | Test        |                   | Phase 3      |
+| 5     | Deploy      |                   | Phase 4      |
+| 6     | Maintain    |                   | Phase 5      |
+
+## Phase 3 Implementation Groups
+
+### Group 1: Foundation
+| Task | Description | Complexity |
+|------|-------------|------------|
+|      |             |            |
+
+### Group 2: Core Features
+| Task | Description | Complexity |
+|------|-------------|------------|
+|      |             |            |
+
+### Group 3: Polish
+| Task | Description | Complexity |
+|------|-------------|------------|
+|      |             |            |
+
+## Timeline Estimate
+
+**Total Estimated Duration:** 
+
+## Milestones
+
+| Milestone | Target Date | Delivered By |
+|-----------|-------------|--------------|
+|           |             |              |
+
+## Risk Assessment
+
+| Risk | Impact | Likelihood | Mitigation |
+|------|--------|------------|------------|
+|      |        |            |            |

package/templates/planning/project-scope.md

@@ -0,0 +1,53 @@
+---
+title: Project Scope
+phase: 1
+status: in-progress
+created: null
+last_updated: null
+stakeholders: []
+user_personas: []
+high_level_goals: []
+constraints: []
+---
+
+# Project Scope
+
+## Aim
+
+<!-- What the project aims to achieve -->
+
+## High-Level Design
+
+<!-- Overview of the solution approach -->
+
+## High-Level Technology Choices
+
+<!-- Major technologies and frameworks chosen -->
+
+## Stakeholders
+
+| Name | Role | Contact |
+|------|------|---------|
+|      |      |         |
+
+## User Personas
+
+| Persona | Description | Needs |
+|---------|-------------|-------|
+|        |             |       |
+
+## High-Level Goals
+
+1. 
+2. 
+3. 
+
+## Constraints
+
+- 
+- 
+
+## Success Criteria
+
+- 
+- 

package/templates/planning/technology-and-architecture.md

@@ -0,0 +1,80 @@
+---
+title: Technology & Architecture
+phase: 1
+status: in-progress
+created: null
+last_updated: null
+architecture_diagram: null
+tech_stack: []
+diagram_type: c4
+---
+
+# Technology & Architecture
+
+## Architecture Diagram
+
+```mermaid
+%% C4 Model Context Diagram
+C4Context
+    title System Context diagram for [System Name]
+
+    Person(personAlias, "Actor Name", "Actor Description")
+    System(systemAlias, "System Name", "System Description")
+
+    Rel(personAlias, systemAlias, "Uses")
+```
+
+<!-- For C4 Level 1 (Context), use:
+     - Person: actors/users
+     - System: the system being built and external systems
+-->
+
+## Technology Stack
+
+| Category | Technology | Version | Rationale |
+|----------|------------|---------|-----------|
+| Language |            |         |           |
+| Framework |          |         |           |
+| Database |           |         |           |
+| Infrastructure |    |         |           |
+| CI/CD |             |         |           |
+| Monitoring |         |         |           |
+
+## Infrastructure Overview
+
+<!-- Describe deployment environment, cloud provider, etc. -->
+
+## System Components
+
+| Component | Responsibility | Technology |
+|-----------|---------------|------------|
+|           |               |            |
+
+## Data Architecture
+
+### Data Stores
+
+| Store | Purpose | Technology |
+|-------|---------|------------|
+|       |         |            |
+
+### Data Flows
+
+```mermaid
+flowchart LR
+    A[Client] --> B[API]
+    B --> C[(Database)]
+```
+
+## Security Considerations
+
+- 
+- 
+
+## Non-Functional Requirements
+
+| Requirement | Target | Measurement |
+|-------------|--------|-------------|
+| Performance |        |             |
+| Availability |       |             |
+| Scalability |        |             |