ZynplexZPX Forgeby Zynplex
For agents.md

Work with me in ZPX Forge

Work in this repository with my agent and subscription. Use Forge to read the customer agreement, coordinate tasks and record the release. The team shares this history across sessions and agents. Stay within the scope I authorize in this chat.

Identify the project

  1. Run zpx version and zpx doctor --json. I can install the CLI with uv tool install zpx or update it with uv tool upgrade zpx.
  2. If access is missing, ask me to enable CLI reports in Team → profile and authorize zpx login in my browser using my GitHub account. Keep credentials on my machine.
  3. Use zpx whoami and zpx projects to identify my account and project. Once confirmed, bind the directory with zpx use COMPANY/PROJECT --here. Replace example identifiers with actual values.
  4. Read zpx context --json. Check the project, responsibilities, plan and agreements under milestones. With permission to configure the repository, run zpx skill install and read the installed AGENTS.md and skills. If harness.sync.required indicates changes, sync and check the context again. Ask me about conflicts with locally edited files.

Before building

Starting from an idea, help me describe the first outcome we can demonstrate to the customer. Starting from an existing repository, CLI 0.2.4 provides zpx audit --json to identify tracked environment files and GitHub Actions workflows in the local index. This diagnostic inspects filenames only.

In Project → Hitos, the editor proposes a testable criterion, demonstration, exclusions, due date and decision maker. That person receives a private sheet to accept the revision or request changes. Work against the last accepted revision. Propose a new revision when the promise changes.

During development

Read zpx today and zpx plan. Open the actual task with zpx task show T003. After I confirm the assignment, use zpx task take T003 and zpx task start T003 --agent codex --branch my-branch with the actual agent and branch. Record progress with zpx task progress T003 "tested outcome". Add --check tests=pass only after running those tests. Record the tested commit and open issues. Use zpx task blocked T003 "reason" for blockers. Consult zpx can-publish BRANCH before publishing and respect the authorization I gave. Keep credentials and customer data out of reports.

Release assurance and acceptance (Pro)

In the milestone, associate the repository and production branch push workflow with the test file and exact job and step names. A reviewer checks whether the test exercises the criterion. Forge queries GitHub for that commit. Each new commit needs its own run. Changing the agreed workflow or test requires renewing the agreement.

Distinguish what the team declared from what Forge observed on GitHub. An accepted risk records the person taking responsibility and their reason. Mark missing CI as pending.

A team member with delivery permission creates the release from the passing milestone. Its owner decides whether to publish a read-only snapshot valid for 30 days. The designated customer signs in with their verified email on the private sheet to accept that version or request corrections. Tell me which version and commit shipped, where I can inspect the evidence and who owns the next decision.

Use zpx help, zpx guide milestone and zpx guide evidence for guidance. Full documentation is available at https://www.zpxforge.com/llms-full.txt.