forge-dev 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- forge_dev-0.1.0/.github/workflows/publish.yml +40 -0
- forge_dev-0.1.0/.gitignore +14 -0
- forge_dev-0.1.0/PKG-INFO +134 -0
- forge_dev-0.1.0/README.md +105 -0
- forge_dev-0.1.0/claude_skill/SKILL.md +171 -0
- forge_dev-0.1.0/forge_core/__init__.py +3 -0
- forge_dev-0.1.0/forge_core/agents/__init__.py +1 -0
- forge_dev-0.1.0/forge_core/auditor.py +330 -0
- forge_dev-0.1.0/forge_core/cli.py +552 -0
- forge_dev-0.1.0/forge_core/detector.py +209 -0
- forge_dev-0.1.0/forge_core/editor_bridge.py +543 -0
- forge_dev-0.1.0/forge_core/models.py +332 -0
- forge_dev-0.1.0/forge_core/phases/__init__.py +1 -0
- forge_dev-0.1.0/forge_core/phases/coherence.py +293 -0
- forge_dev-0.1.0/forge_core/phases/context.py +264 -0
- forge_dev-0.1.0/forge_core/phases/intake.py +340 -0
- forge_dev-0.1.0/forge_core/registry.py +247 -0
- forge_dev-0.1.0/forge_core/standards/api-first-design.yaml +24 -0
- forge_dev-0.1.0/forge_core/standards/microservice-packaging.yaml +30 -0
- forge_dev-0.1.0/forge_core/standards/observability.yaml +31 -0
- forge_dev-0.1.0/forge_core/standards/security-baseline.yaml +43 -0
- forge_dev-0.1.0/forge_core/standards/type-safety.yaml +23 -0
- forge_dev-0.1.0/forge_core/templates/__init__.py +1 -0
- forge_dev-0.1.0/forge_core/utils/__init__.py +1 -0
- forge_dev-0.1.0/mcp_server/__init__.py +1 -0
- forge_dev-0.1.0/mcp_server/server.py +1086 -0
- forge_dev-0.1.0/pyproject.toml +65 -0
- forge_dev-0.1.0/references/implementation-phases.md +157 -0
- forge_dev-0.1.0/setup.sh +87 -0
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
name: Publish to PyPI
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
release:
|
|
5
|
+
types: [published]
|
|
6
|
+
workflow_dispatch:
|
|
7
|
+
|
|
8
|
+
jobs:
|
|
9
|
+
build:
|
|
10
|
+
name: Build distribution
|
|
11
|
+
runs-on: ubuntu-latest
|
|
12
|
+
steps:
|
|
13
|
+
- uses: actions/checkout@v4
|
|
14
|
+
- uses: actions/setup-python@v5
|
|
15
|
+
with:
|
|
16
|
+
python-version: "3.12"
|
|
17
|
+
- name: Install build tools
|
|
18
|
+
run: python -m pip install --upgrade build
|
|
19
|
+
- name: Build package
|
|
20
|
+
run: python -m build
|
|
21
|
+
- uses: actions/upload-artifact@v4
|
|
22
|
+
with:
|
|
23
|
+
name: dist
|
|
24
|
+
path: dist/
|
|
25
|
+
|
|
26
|
+
publish:
|
|
27
|
+
name: Publish to PyPI
|
|
28
|
+
needs: build
|
|
29
|
+
runs-on: ubuntu-latest
|
|
30
|
+
environment:
|
|
31
|
+
name: pypi
|
|
32
|
+
url: https://pypi.org/p/forge-dev
|
|
33
|
+
permissions:
|
|
34
|
+
id-token: write
|
|
35
|
+
steps:
|
|
36
|
+
- uses: actions/download-artifact@v4
|
|
37
|
+
with:
|
|
38
|
+
name: dist
|
|
39
|
+
path: dist/
|
|
40
|
+
- uses: pypa/gh-action-pypi-publish@release/v1
|
forge_dev-0.1.0/PKG-INFO
ADDED
|
@@ -0,0 +1,134 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: forge-dev
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: AI-Native Development Workflow Engine
|
|
5
|
+
Author: NaiaTech
|
|
6
|
+
License-Expression: MIT
|
|
7
|
+
Keywords: ai,development,mcp,scaffold,workflow
|
|
8
|
+
Classifier: Development Status :: 3 - Alpha
|
|
9
|
+
Classifier: Intended Audience :: Developers
|
|
10
|
+
Classifier: License :: OSI Approved :: MIT License
|
|
11
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
12
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
13
|
+
Classifier: Topic :: Software Development :: Code Generators
|
|
14
|
+
Requires-Python: >=3.11
|
|
15
|
+
Requires-Dist: click>=8.1.0
|
|
16
|
+
Requires-Dist: gitpython>=3.1.0
|
|
17
|
+
Requires-Dist: httpx>=0.27.0
|
|
18
|
+
Requires-Dist: jinja2>=3.1
|
|
19
|
+
Requires-Dist: mcp>=1.0.0
|
|
20
|
+
Requires-Dist: pydantic>=2.0
|
|
21
|
+
Requires-Dist: pyyaml>=6.0
|
|
22
|
+
Requires-Dist: rich>=13.0
|
|
23
|
+
Provides-Extra: dev
|
|
24
|
+
Requires-Dist: mypy>=1.10; extra == 'dev'
|
|
25
|
+
Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
|
|
26
|
+
Requires-Dist: pytest>=8.0; extra == 'dev'
|
|
27
|
+
Requires-Dist: ruff>=0.4; extra == 'dev'
|
|
28
|
+
Description-Content-Type: text/markdown
|
|
29
|
+
|
|
30
|
+
# Forge — AI-Native Development Workflow Engine
|
|
31
|
+
|
|
32
|
+
Forge is a development workflow system that transforms requirements into production-ready, audited, observable code. It is designed exclusively for AI-assisted development, optimizing every step for how AI coding agents work.
|
|
33
|
+
|
|
34
|
+
## Philosophy
|
|
35
|
+
|
|
36
|
+
Forge encodes a complete development paradigm — from receiving a vague requirement to deploying a fully observable SaaS application. It handles all the non-functional requirements (security, observability, auth, API design, compliance) so you can focus on business logic.
|
|
37
|
+
|
|
38
|
+
**Core principles:**
|
|
39
|
+
- Requirements in, production code out
|
|
40
|
+
- Strong defaults, flexible overrides
|
|
41
|
+
- Every project starts with everything (observability, auth, CI/CD, IaC)
|
|
42
|
+
- AI-coding-agent-first task ordering
|
|
43
|
+
- Continuous auditing — not just at the end
|
|
44
|
+
- API-first, MCP-ready, repackageable microservices
|
|
45
|
+
- The workflow evolves and versions itself
|
|
46
|
+
|
|
47
|
+
## Installation
|
|
48
|
+
|
|
49
|
+
```bash
|
|
50
|
+
pip install forge-dev
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
Or install from source:
|
|
54
|
+
|
|
55
|
+
```bash
|
|
56
|
+
git clone https://github.com/<org>/forge.git
|
|
57
|
+
cd forge
|
|
58
|
+
pip install -e .
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
## Quick Start
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
# New project — empty folder
|
|
65
|
+
cd my-new-project
|
|
66
|
+
forge init
|
|
67
|
+
|
|
68
|
+
# New project — with requirements doc
|
|
69
|
+
cd my-new-project
|
|
70
|
+
cp ~/requirements.md .
|
|
71
|
+
forge init
|
|
72
|
+
|
|
73
|
+
# Existing project — assess maturity
|
|
74
|
+
cd my-existing-project
|
|
75
|
+
forge assess
|
|
76
|
+
|
|
77
|
+
# Upgrade Forge to latest version
|
|
78
|
+
forge upgrade
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
## Commands
|
|
82
|
+
|
|
83
|
+
| Command | Description |
|
|
84
|
+
|---------|-------------|
|
|
85
|
+
| `forge init` | Initialize Forge in a project (detects context automatically) |
|
|
86
|
+
| `forge intake <file>` | Process a requirement document into a Forge Brief |
|
|
87
|
+
| `forge plan` | Generate AI-optimized implementation plan |
|
|
88
|
+
| `forge audit` | Run all audit agents against current code |
|
|
89
|
+
| `forge assess` | Evaluate existing project against current standards |
|
|
90
|
+
| `forge upgrade` | Update Forge core from upstream |
|
|
91
|
+
| `forge journal` | Add learnings/nuances to project journal |
|
|
92
|
+
| `forge status` | Show current project state and plan progress |
|
|
93
|
+
| `forge standards` | View, add, or modify standards |
|
|
94
|
+
| `forge mcps` | View or configure recommended MCPs |
|
|
95
|
+
|
|
96
|
+
## Architecture
|
|
97
|
+
|
|
98
|
+
```
|
|
99
|
+
~/.forge/ ← Global Forge installation
|
|
100
|
+
├── core/ ← Upstream (updated via forge upgrade)
|
|
101
|
+
│ ├── VERSION
|
|
102
|
+
│ ├── phases/ ← Workflow phase definitions
|
|
103
|
+
│ ├── agents/ ← Audit agent configurations
|
|
104
|
+
│ ├── templates/ ← Project scaffold templates
|
|
105
|
+
│ └── standards/ ← Base standards
|
|
106
|
+
├── user/ ← Your customizations (never touched by upgrade)
|
|
107
|
+
│ ├── config.yaml ← Your defaults (cloud, stack, preferences)
|
|
108
|
+
│ ├── standards/ ← Standards you've added
|
|
109
|
+
│ ├── patterns/ ← Approved patterns with code examples
|
|
110
|
+
│ ├── anti-patterns/ ← Things to never do
|
|
111
|
+
│ ├── mcps.yaml ← Your MCP registry
|
|
112
|
+
│ └── history/ ← Project history and learnings
|
|
113
|
+
|
|
114
|
+
project/.forge/ ← Per-project Forge state
|
|
115
|
+
├── context.yaml ← Stack, infra, decisions
|
|
116
|
+
├── brief.md ← Normalized requirement
|
|
117
|
+
├── plan.yaml ← AI-optimized implementation plan
|
|
118
|
+
├── journal.md ← Project-specific learnings
|
|
119
|
+
├── overrides/ ← Local standard overrides
|
|
120
|
+
├── audit/ ← Audit logs
|
|
121
|
+
└── maturity.yaml ← Assessment results
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
## MCP Server
|
|
125
|
+
|
|
126
|
+
Forge also runs as an MCP server, making it accessible from any editor (Cursor, Copilot, Windsurf, etc.):
|
|
127
|
+
|
|
128
|
+
```bash
|
|
129
|
+
forge mcp start
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
## License
|
|
133
|
+
|
|
134
|
+
MIT
|
|
@@ -0,0 +1,105 @@
|
|
|
1
|
+
# Forge — AI-Native Development Workflow Engine
|
|
2
|
+
|
|
3
|
+
Forge is a development workflow system that transforms requirements into production-ready, audited, observable code. It is designed exclusively for AI-assisted development, optimizing every step for how AI coding agents work.
|
|
4
|
+
|
|
5
|
+
## Philosophy
|
|
6
|
+
|
|
7
|
+
Forge encodes a complete development paradigm — from receiving a vague requirement to deploying a fully observable SaaS application. It handles all the non-functional requirements (security, observability, auth, API design, compliance) so you can focus on business logic.
|
|
8
|
+
|
|
9
|
+
**Core principles:**
|
|
10
|
+
- Requirements in, production code out
|
|
11
|
+
- Strong defaults, flexible overrides
|
|
12
|
+
- Every project starts with everything (observability, auth, CI/CD, IaC)
|
|
13
|
+
- AI-coding-agent-first task ordering
|
|
14
|
+
- Continuous auditing — not just at the end
|
|
15
|
+
- API-first, MCP-ready, repackageable microservices
|
|
16
|
+
- The workflow evolves and versions itself
|
|
17
|
+
|
|
18
|
+
## Installation
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
pip install forge-dev
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
Or install from source:
|
|
25
|
+
|
|
26
|
+
```bash
|
|
27
|
+
git clone https://github.com/<org>/forge.git
|
|
28
|
+
cd forge
|
|
29
|
+
pip install -e .
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
## Quick Start
|
|
33
|
+
|
|
34
|
+
```bash
|
|
35
|
+
# New project — empty folder
|
|
36
|
+
cd my-new-project
|
|
37
|
+
forge init
|
|
38
|
+
|
|
39
|
+
# New project — with requirements doc
|
|
40
|
+
cd my-new-project
|
|
41
|
+
cp ~/requirements.md .
|
|
42
|
+
forge init
|
|
43
|
+
|
|
44
|
+
# Existing project — assess maturity
|
|
45
|
+
cd my-existing-project
|
|
46
|
+
forge assess
|
|
47
|
+
|
|
48
|
+
# Upgrade Forge to latest version
|
|
49
|
+
forge upgrade
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
## Commands
|
|
53
|
+
|
|
54
|
+
| Command | Description |
|
|
55
|
+
|---------|-------------|
|
|
56
|
+
| `forge init` | Initialize Forge in a project (detects context automatically) |
|
|
57
|
+
| `forge intake <file>` | Process a requirement document into a Forge Brief |
|
|
58
|
+
| `forge plan` | Generate AI-optimized implementation plan |
|
|
59
|
+
| `forge audit` | Run all audit agents against current code |
|
|
60
|
+
| `forge assess` | Evaluate existing project against current standards |
|
|
61
|
+
| `forge upgrade` | Update Forge core from upstream |
|
|
62
|
+
| `forge journal` | Add learnings/nuances to project journal |
|
|
63
|
+
| `forge status` | Show current project state and plan progress |
|
|
64
|
+
| `forge standards` | View, add, or modify standards |
|
|
65
|
+
| `forge mcps` | View or configure recommended MCPs |
|
|
66
|
+
|
|
67
|
+
## Architecture
|
|
68
|
+
|
|
69
|
+
```
|
|
70
|
+
~/.forge/ ← Global Forge installation
|
|
71
|
+
├── core/ ← Upstream (updated via forge upgrade)
|
|
72
|
+
│ ├── VERSION
|
|
73
|
+
│ ├── phases/ ← Workflow phase definitions
|
|
74
|
+
│ ├── agents/ ← Audit agent configurations
|
|
75
|
+
│ ├── templates/ ← Project scaffold templates
|
|
76
|
+
│ └── standards/ ← Base standards
|
|
77
|
+
├── user/ ← Your customizations (never touched by upgrade)
|
|
78
|
+
│ ├── config.yaml ← Your defaults (cloud, stack, preferences)
|
|
79
|
+
│ ├── standards/ ← Standards you've added
|
|
80
|
+
│ ├── patterns/ ← Approved patterns with code examples
|
|
81
|
+
│ ├── anti-patterns/ ← Things to never do
|
|
82
|
+
│ ├── mcps.yaml ← Your MCP registry
|
|
83
|
+
│ └── history/ ← Project history and learnings
|
|
84
|
+
|
|
85
|
+
project/.forge/ ← Per-project Forge state
|
|
86
|
+
├── context.yaml ← Stack, infra, decisions
|
|
87
|
+
├── brief.md ← Normalized requirement
|
|
88
|
+
├── plan.yaml ← AI-optimized implementation plan
|
|
89
|
+
├── journal.md ← Project-specific learnings
|
|
90
|
+
├── overrides/ ← Local standard overrides
|
|
91
|
+
├── audit/ ← Audit logs
|
|
92
|
+
└── maturity.yaml ← Assessment results
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
## MCP Server
|
|
96
|
+
|
|
97
|
+
Forge also runs as an MCP server, making it accessible from any editor (Cursor, Copilot, Windsurf, etc.):
|
|
98
|
+
|
|
99
|
+
```bash
|
|
100
|
+
forge mcp start
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
## License
|
|
104
|
+
|
|
105
|
+
MIT
|
|
@@ -0,0 +1,171 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: forge
|
|
3
|
+
description: AI-Native Development Workflow Engine. Use this skill whenever starting a new project, processing requirements, scaffolding code, auditing existing code, or managing development standards. Triggers on phrases like "new project", "initialize", "scaffold", "set up", "forge", "requirement analysis", "implementation plan", "audit code", "assess project", "add standard", "maturity assessment", or any request to create a full project from a requirement. Also triggers when the user mentions PRDs, user stories, epics, or asks about implementation ordering for AI coding agents. Use this skill proactively when the user is about to start coding without a clear plan or project structure.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Forge — AI-Native Development Workflow Engine
|
|
7
|
+
|
|
8
|
+
## Overview
|
|
9
|
+
|
|
10
|
+
Forge transforms requirements into production-ready, audited, observable code. It handles all non-functional requirements (security, observability, auth, API design, compliance) so you focus on business logic.
|
|
11
|
+
|
|
12
|
+
**Core philosophy**: Requirements in, production code out. Strong defaults, flexible overrides. AI-coding-agent-first task ordering. Continuous auditing.
|
|
13
|
+
|
|
14
|
+
## When To Use Forge
|
|
15
|
+
|
|
16
|
+
- Starting any new project or feature
|
|
17
|
+
- Processing a requirement document (PRD, user story, epic, etc.)
|
|
18
|
+
- Setting up project scaffolding with full observability, auth, CI/CD
|
|
19
|
+
- Auditing existing code against standards
|
|
20
|
+
- Assessing project maturity
|
|
21
|
+
- Adding or managing development standards
|
|
22
|
+
- Planning implementation order for AI coding agents
|
|
23
|
+
|
|
24
|
+
## Quick Start
|
|
25
|
+
|
|
26
|
+
### 1. Initialize a Project
|
|
27
|
+
|
|
28
|
+
In the project directory, run:
|
|
29
|
+
|
|
30
|
+
```bash
|
|
31
|
+
forge init
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
This detects the directory state:
|
|
35
|
+
- **Empty**: Guided setup — asks about mission, stack, regulatory requirements
|
|
36
|
+
- **Has docs**: Analyzes documents, suggests processing them with `forge intake`
|
|
37
|
+
- **Has code**: Detects stack, offers assessment
|
|
38
|
+
- **Has .forge/**: Already initialized, shows status
|
|
39
|
+
|
|
40
|
+
### 2. Process a Requirement
|
|
41
|
+
|
|
42
|
+
```bash
|
|
43
|
+
forge intake requirements.md
|
|
44
|
+
# or
|
|
45
|
+
forge intake --text "Build a multi-tenant SaaS for..."
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
This classifies the requirement (PRD, user story, epic, etc.) and generates an intake prompt for LLM analysis that produces a Forge Brief with:
|
|
49
|
+
- Normalized features and MVP scope
|
|
50
|
+
- Gap detection with suggestions
|
|
51
|
+
- AI-optimized implementation ordering
|
|
52
|
+
|
|
53
|
+
### 3. Check Status
|
|
54
|
+
|
|
55
|
+
```bash
|
|
56
|
+
forge status
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
### 4. Add Journal Entries
|
|
60
|
+
|
|
61
|
+
Record project-specific learnings:
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
forge journal "Azure DB requires pg tunnel via temp install"
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
### 5. Manage Standards
|
|
68
|
+
|
|
69
|
+
```bash
|
|
70
|
+
forge standards --name "API Versioning" --area "api-design" --description "All APIs must use URL-prefix versioning (e.g., /v1/users)"
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
Standards are coherence-checked before being added.
|
|
74
|
+
|
|
75
|
+
## Architecture
|
|
76
|
+
|
|
77
|
+
### Global Registry (~/.forge/)
|
|
78
|
+
|
|
79
|
+
```
|
|
80
|
+
~/.forge/
|
|
81
|
+
├── core/ ← Upstream (updated via forge upgrade)
|
|
82
|
+
│ ├── VERSION
|
|
83
|
+
│ ├── phases/ ← Workflow phase definitions
|
|
84
|
+
│ ├── agents/ ← Audit agent configurations
|
|
85
|
+
│ ├── templates/ ← Project scaffold templates
|
|
86
|
+
│ └── standards/ ← Base standards
|
|
87
|
+
├── user/ ← Your customizations (never touched by upgrade)
|
|
88
|
+
│ ├── config.yaml
|
|
89
|
+
│ ├── standards/
|
|
90
|
+
│ ├── patterns/
|
|
91
|
+
│ ├── anti-patterns/
|
|
92
|
+
│ ├── mcps.yaml
|
|
93
|
+
│ └── history/
|
|
94
|
+
└── versions/ ← Workflow version snapshots
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
### Per-Project (.forge/)
|
|
98
|
+
|
|
99
|
+
```
|
|
100
|
+
.forge/
|
|
101
|
+
├── context.yaml ← Stack, infra, all decisions
|
|
102
|
+
├── brief.yaml ← Normalized requirement
|
|
103
|
+
├── plan.yaml ← AI-optimized implementation plan
|
|
104
|
+
├── journal.md ← Project-specific learnings
|
|
105
|
+
├── overrides/ ← Local standard overrides
|
|
106
|
+
└── audit/ ← Audit logs
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
## AI-Optimized Implementation Order
|
|
110
|
+
|
|
111
|
+
Forge orders implementation to minimize AI coding agent hallucinations:
|
|
112
|
+
|
|
113
|
+
1. **Types & Contracts** — Pydantic models, TypeScript interfaces, OpenAPI schemas
|
|
114
|
+
2. **Infrastructure** — IaC, environment configs, secrets
|
|
115
|
+
3. **Auth & Security** — Auth flows, RBAC, middleware
|
|
116
|
+
4. **Data Layer** — ORM models, migrations, repositories
|
|
117
|
+
5. **Core Services** — Business logic (no HTTP concerns)
|
|
118
|
+
6. **API Layer** — Endpoints exposing services (OpenAPI-documented, MCP-ready)
|
|
119
|
+
7. **Frontend** — Components, pages, state management
|
|
120
|
+
8. **Observability** — APM, metrics, logs, dashboards, AI tracking
|
|
121
|
+
9. **Testing** — Unit, integration, E2E
|
|
122
|
+
10. **CI/CD & Deploy** — Pipelines, IaC execution, smoke tests
|
|
123
|
+
|
|
124
|
+
Each phase has complete context from all previous phases, reducing hallucinations.
|
|
125
|
+
|
|
126
|
+
## Default Stack (User Configurable)
|
|
127
|
+
|
|
128
|
+
These defaults are stored in `~/.forge/user/config.yaml`:
|
|
129
|
+
|
|
130
|
+
- **Cloud**: Azure
|
|
131
|
+
- **Backend**: Ask each time (FastAPI, Django, Express, Fastify, NestJS)
|
|
132
|
+
- **Frontend**: React
|
|
133
|
+
- **Database**: PostgreSQL
|
|
134
|
+
- **Auth**: Azure AD B2C
|
|
135
|
+
- **Observability**: App Insights + Prometheus + Loki + Grafana
|
|
136
|
+
- **API**: REST, OpenAPI 3.1, MCP-ready, URL-prefix versioning
|
|
137
|
+
- **CI/CD**: GitHub Actions + Pulumi
|
|
138
|
+
- **Standards**: Strict type checking, enforced linting, 80% coverage minimum
|
|
139
|
+
|
|
140
|
+
Override any default per-project in `.forge/context.yaml`.
|
|
141
|
+
|
|
142
|
+
## MCP Server
|
|
143
|
+
|
|
144
|
+
Forge runs as an MCP server for editor integration:
|
|
145
|
+
|
|
146
|
+
```bash
|
|
147
|
+
python mcp_server/server.py
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
Exposes tools: `forge_init`, `forge_intake`, `forge_status`, `forge_journal`, `forge_standards_add`, `forge_coherence_check`, `forge_mcps_list`, etc.
|
|
151
|
+
|
|
152
|
+
## Key Commands Reference
|
|
153
|
+
|
|
154
|
+
| Command | What it does |
|
|
155
|
+
|---------|-------------|
|
|
156
|
+
| `forge init` | Initialize project, detect context |
|
|
157
|
+
| `forge intake <file>` | Process requirement → Forge Brief |
|
|
158
|
+
| `forge plan` | Generate AI-optimized task plan |
|
|
159
|
+
| `forge audit` | Run audit agents on current code |
|
|
160
|
+
| `forge assess` | Maturity assessment for existing project |
|
|
161
|
+
| `forge upgrade` | Update Forge core from upstream |
|
|
162
|
+
| `forge journal` | Add project-specific learning |
|
|
163
|
+
| `forge standards` | Add standard (with coherence check) |
|
|
164
|
+
| `forge mcps` | View/manage MCP registry |
|
|
165
|
+
| `forge status` | Show project state |
|
|
166
|
+
|
|
167
|
+
## References
|
|
168
|
+
|
|
169
|
+
- See `references/implementation-phases.md` for detailed phase documentation
|
|
170
|
+
- See `references/standards-guide.md` for writing effective standards
|
|
171
|
+
- See `references/audit-agents.md` for agent configuration
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
"""Forge audit agents."""
|