Set up a project from your repository

A project is where all work happens, so the better it describes your application, the better every agent works in it. The fastest way to fill it is to let a coding agent read the repository you already have, then ask you for the rest: wikis, runbooks, dashboards, and the rules agents must follow.

You get: a project with a description, standing instructions, typed links to your sources and wikis, uploaded documents, and a repository folder that targets the project automatically.

Time: about 10 minutes.

Before you start

• The CLI and skill are installed and stratonext whoami works.
• Your coding agent (Claude Code, Codex, or similar) is opened in the root folder of your repository.
• Optional: the URLs of your wiki, runbooks, and dashboards, for example Confluence, Notion, Google Docs, or Grafana pages.

Paste this prompt

Using the StratoNext skill, set up a new StratoNext project for the application in this repository.

1. Read this repository (README, docs folder, infrastructure code, CI config) and propose a project name, a short description, and standing instructions for agents (conventions, guardrails, what never to touch). Show them to me before creating anything.
2. Create the project and make it the default for this folder with a local .stratonext file.
3. Add this repository as a SOURCE_CODE link, using its remote URL.
4. Ask me for our wikis, runbooks, dashboards, and other tools, and add each one as a typed link.
5. Upload the most useful documents from the repository (architecture notes, runbooks, diagrams) as project assets. Ask me before uploading anything that may contain secrets.
6. Record anything you could not find as a project note.
7. Read the finished project back to me.

What the agent does

The agent runs every step below for you. Nothing here is for you to type. Expand a step to see examples of the commands it might run. The exact calls depend on what it finds in your setup.

1. Creates the project. After you confirm the proposal:

Example commands the agent might run

stratonext project create --name "Orders API" \
  --description "Order intake and payment service for the web shop" --type SOFTWARE_APPLICATION

2. Links this folder to the project. This writes a .stratonext file at the repository root. Commit it, and every stratonext command run in this repository, by you or a teammate, targets the project without passing --project-id.

Example commands the agent might run

stratonext project use <project_id> --local

3. Sets the standing instructions. These are rules every agent reads before working in the project:

Example commands the agent might run

stratonext project update --instructions "Production runs in us-east-1. Never restart the payments worker during business hours. Runbooks live in the Ops wiki."

4. Connects your existing sources and wikis. Each link gets a type, so agents know what it is:

Example commands the agent might run

stratonext project add-link --url https://github.com/acme/orders-api --name "Orders API repository" --type SOURCE_CODE
stratonext project add-link --url https://acme.atlassian.net/wiki/spaces/OPS --name "Ops wiki" --type DOCUMENTATION
stratonext project add-link --url https://grafana.acme.com/d/orders --name "Orders dashboard" --type TOOL

5. Uploads documents. Files that agents should read in full go in as project assets:

Example commands the agent might run

stratonext asset upload docs/architecture.md --parent-type PROJECT --parent-id <project_id>
stratonext asset upload docs/runbooks/incident-response.md --parent-type PROJECT --parent-id <project_id>

If a document lives somewhere the agent cannot read, such as a private drive, it adds a link to it instead.

6. Notes the gaps.

Example commands the agent might run

stratonext project add-note --text "No runbook yet for the nightly settlement job."

Link the repository through GitHub (optional)

If an admin has connected GitHub to your organization, link the repository to the project too. StratoNext then shows its recent commits and branches, and builds a dependency graph from its catalog-info.yaml. Add this line to the prompt above, or ask afterwards:

Also link this repository to the project through our GitHub connection.

The agent finds the repository and links it.

Example commands the agent might run

stratonext workspace git get
stratonext workspace git repos
stratonext project repo link --connection-id <connection_id> --repo-id <repo_id> --repo-full-name acme/orders-api

Check the result

stratonext project get

Open the project in the web app to see the same links, notes, and documents. Repeat this guide in each repository you want as its own project.

Tip

Several repositories that ship together, such as a frontend and an API, usually belong in one project. Open the agent in each repository, link it to the same project with stratonext project use <project_id> --local, and add its links.

Next step

Connect your cloud account so agents can see what the project runs on.