npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

forgeai-workflow

v0.1.9

Published

AI-first agentic engineering workflow for software engineering projects

Downloads

729

Readme

ForgeAI

AI-first agentic engineering workflow for software engineering projects.

ForgeAI gives your project a team of specialized AI engineering agents that work through a structured workflow or can be invoked standalone. Built for Claude Code and GitHub Copilot, with cross-tool support for Cursor, Codex, and Google Jules via AGENTS.md.


Quick Start

npx forgeai-workflow init

How-To Guides

Full walkthroughs with verbatim agent conversations for every scenario:

  • HOWTOClaude.md — Claude Code guide (blog from scratch, existing apps, resuming, standalone agents, QA, health scans)
  • HOWTOCopilot.md — GitHub Copilot guide (same scenarios, Copilot-specific commands)

The Team

| Agent | Name | Role | Core Responsibility | |-------|------|------|-------------------| | Orchestrator | Jabari | Project coordinator | Runs the workflow, enforces quality checkpoints, routes tasks | | Codebase Docs | Amina | Documentation | Scans and documents codebases — no assumptions. Architecture health scans. | | Analyst | Imani | Requirements | PRDs, user stories, acceptance criteria, quality targets | | Architect | Zuberi | System design | Architecture, ADRs, Mermaid diagrams, API design | | Designer | Zuri | UX/UI | User flows, screen specs, accessibility | | Test Engineer | Kofi | TDD | Written test plan → failing tests — confirms all failing before handoff | | Engineer | Rashidi | Implementation | Makes tests pass, runs complexity check — minimal diff | | QA | Neema | Browser testing | Playwright-driven QA, health scores, bug fix workflow | | DevOps Azure | Faraji | Delivery | CI/CD, Azure infrastructure, IaC |


Two Paths

Prescribed Workflow

Jabari (Orchestrator) guides you through the full engineering lifecycle with hard quality checkpoints. Kofi (Test Engineer) must write and confirm all tests are failing before Rashidi (Engineer) writes any implementation code — this is non-negotiable.

Requirements → [Spec check] → Architecture → Design → [Test plan] → Tests → Implementation → [Complexity check] → QA → Deploy

Claude Code:

/forge-orchestrate       # Let Jabari (Orchestrator) drive everything
/forge-requirements      # Imani (Analyst)
/forge-architecture      # Zuberi (Architect)
/forge-design            # Zuri (Designer)
/forge-testing           # Kofi (Test Engineer)
/forge-implementation    # Rashidi (Engineer)
/forge-deployment        # Faraji (DevOps Azure)
/forge-document-codebase # Standalone: scan and document an existing codebase

GitHub Copilot:

/forge/orchestrate       # Let Jabari (Orchestrator) drive everything
/forge/requirements      # Imani (Analyst)
/forge/architecture      # Zuberi (Architect)
/forge/design            # Zuri (Designer)
/forge/testing           # Kofi (Test Engineer)
/forge/implementation    # Rashidi (Engineer)
/forge/deployment        # Faraji (DevOps Azure)

Standalone

Invoke any agent directly for a specific task:

Claude Code:

@orchestrator
@analyst
@architect
@designer
@test-engineer
@engineer
@qa
@devops-azure
@codebase-docs

Copilot Chat:

@orchestrator   start the ForgeAI workflow
@analyst        write a PRD for user authentication
@architect      review the current system design and produce ADRs
@designer       spec the UI for the login flow
@test-engineer  write failing tests for the payment module
@engineer       implement the payment module so all tests pass
@qa             run a full browser QA pass on the current build
@devops-azure   create a CI/CD pipeline for this Node.js app

Test-First Contract

ForgeAI enforces TDD through an explicit handoff contract:

1. Jabari (Orchestrator) → Kofi (Test Engineer)    "Write failing tests for [feature]"
2. Kofi (Test Engineer)  → Jabari (Orchestrator)   "Tests written — all failing"
3. Jabari (Orchestrator) → Rashidi (Engineer)      "Make these tests pass. Do not write tests."
4. Rashidi (Engineer)    → Jabari (Orchestrator)   "Implementation complete — all tests passing"
5. Jabari (Orchestrator) → Neema (QA)              "Browser-test the feature"
6. Neema (QA)            → Jabari (Orchestrator)   "Browser QA complete"

Neither Rashidi (Engineer) nor Jabari (Orchestrator) may skip step 2.


Quality Enforcement

ForgeAI embeds quality constraints at every phase — not just at the end.

Spec completeness gate — Before architecture starts, Jabari (Orchestrator) validates design.md: every FR must have a GIVEN/WHEN/THEN acceptance criterion, Non-Goals must be defined, and no vague language ("fast", "easy", "better") without a measurable number.

Default quality targets — Imani (Analyst) writes these into design.md as binding constraints:

| Target | Default | |--------|---------| | Test coverage | ≥ 85% branch | | Cyclomatic complexity | ≤ 10 per function (≥ 20 = blocker) | | Static analysis | 0 critical findings before merge |

Written test plan — Kofi (Test Engineer) produces a FR → test type → file → test name plan for every requirement, approved by you before a single test is written.

Complexity check — After all tests pass, Rashidi (Engineer) runs a complexity scan on every modified file. Functions with complexity ≥ 20 block the completion gate.

Anti-Slop Contract — All agents enforce five explicit prohibitions: no obvious comments, no unnecessary defensive code, no type workarounds, no pattern drift, no over-engineering.


What Gets Installed

AGENTS.md                          ← cross-tool (Cursor, Codex, Jules, Copilot, Claude)
CLAUDE.md                          ← Claude Code workspace instructions

Claude Code

.claude/
├── agents/
│   ├── orchestrator.md
│   ├── codebase-docs.md
│   ├── analyst.md
│   ├── architect.md
│   ├── designer.md
│   ├── test-engineer.md
│   ├── engineer.md
│   ├── qa.md
│   └── devops-azure.md
└── commands/
    ├── forge-orchestrate.md
    ├── forge-requirements.md
    ├── forge-architecture.md
    ├── forge-design.md
    ├── forge-testing.md
    ├── forge-implementation.md
    └── forge-deployment.md

GitHub Copilot

.github/
├── copilot-instructions.md
├── agents/
│   ├── orchestrator.agent.md
│   ├── codebase-docs.agent.md
│   ├── analyst.agent.md
│   ├── architect.agent.md
│   ├── designer.agent.md
│   ├── test-engineer.agent.md
│   ├── engineer.agent.md
│   ├── qa.agent.md
│   └── devops-azure.agent.md
└── prompts/
    └── forge/
        ├── orchestrate.prompt.md
        ├── requirements.prompt.md
        ├── architecture.prompt.md
        ├── design.prompt.md
        ├── testing.prompt.md
        ├── implementation.prompt.md
        └── deployment.prompt.md

Core Principles

  1. Orchestrator owns the workflow — agents do not self-assign tasks or skip checkpoints
  2. Test-first is non-negotiable — no implementation without a written, approved test plan and confirmed failing tests
  3. Smallest possible diff — Rashidi (Engineer) never reformats or refactors unrelated code
  4. Design.md is the source of truth — all agents read it before acting; quality targets inside it are binding
  5. Explicit over implicit — every handoff has a written confirmation message
  6. Quality is quantified — coverage, complexity, and static analysis thresholds are set in the spec, enforced by agents
  7. Anti-slop by default — explicit prohibitions prevent padding, unnecessary code, and pattern drift

Inspired By


License

MIT