---
generator: "vaultspec-marketing discovery"
title: "Run a feature with your agent - Vaultspec documentation"
description: "Start from the documentation home to install Core and create a record. Then connect your agent so it can read and update project records."
url: "https://vaultspec.neve.md/docs/guides/workflow.html"
component: "site"

---

[View as Markdown](<https://vaultspec.neve.md/docs/guides/workflow.md>)

# Run a feature with your agent

Start from the [documentation home](<https://vaultspec.neve.md/docs/index.html>) to install Core and create a record. Then [connect your agent](<https://vaultspec.neve.md/docs/guides/mcp.html>) so it can read and update project records.

## Check the starting point

Use this prompt to check the connection and find existing work:

**Prompt for your agent**

```
Use the vaultspec-core MCP status tool to show the status of this project. Tell me which features exist and whether any plan is in flight. Do not change any files.
```

In the tested quickstart project, Codex called the Core status tool and reported one `notes-search` research record and no plan. If the tool is unavailable, use the [connection checks](<https://vaultspec.neve.md/docs/guides/mcp.html#check-that-it-connected>).

## Start a feature record

If you completed the quickstart, keep its `notes-search` record. In a project that does not have that record yet, this prompt starts it through the agent:

**Prompt for your agent**

```
Use the vaultspec-core MCP create tool to create a research record with feature notes-search and title Search project notes. Report the created path. Do not implement code.
```

The tested Codex session created the dated Markdown file and returned its path. Open it to see the research template. It still needs the question, findings, and sources; creating it does not perform the investigation.

## Move from a question to reviewed work

The installed skills describe the workflow. Each stage has a different result:

| Stage | What you review | Installed skill |
| --- | --- | --- |
| Investigate | Evidence, existing behavior, and alternatives | `vaultspec-research` or `vaultspec-code-research` |
| Decide | A proposed architecture decision record (ADR), when a decision needs one | `vaultspec-adr` |
| Plan | Scoped steps and how each will be checked | `vaultspec-write` |
| Implement | Code changes and recorded verification for the approved steps | `vaultspec-execute` |
| Review | Findings against the implementation | `vaultspec-code-review` |

Review the proposed decision and plan before authorizing implementation. Existing decisions and sufficient evidence can be reused; a small task need not create every kind of record. [How vaultspec works](<https://vaultspec.neve.md/docs/concepts.html>) explains these terms.

These are skill responsibilities, not a fixed sequence of chat messages. The agent’s tools, project instructions, and your authorization affect what happens next. The two tested prompts check status and create a record. They do not run the complete feature workflow.

## Check progress and the result

**Command**

```sh
uvx vaultspec-core status
uvx vaultspec-core vault list --feature notes-search
```

Keep the feature tag consistent so its records stay grouped. If you used another tag, substitute it for `notes-search`.

Read the code diff and actual test results alongside the records. A checked step or a clean record check does not establish that the implementation works. See [review and correctness](<https://vaultspec.neve.md/docs/core/correctness.html>).

## Where to go next

Use the [command-line guide](<https://vaultspec.neve.md/docs/guides/cli.html>) to create and find records yourself. The [CLI reference](<https://vaultspec.neve.md/docs/core/cli.html>) covers plan editing and execution logging; [workspace verification](<https://vaultspec.neve.md/docs/core/verification.html>) covers record checks.