Build features

Add a feature the way Xaden expects: from a requirement, test first, checked before every commit. Repeat for every feature.

Before you start

You finished the kickoff, so the project has approved requirements and a stack with working checks.

Build one feature

Start it with:

/feature <what users can do afterwards>

$feature <what users can do afterwards>

/feature <what users can do afterwards>

/feature <what users can do afterwards>

Run `xaden prompt feature` and follow it. Feature: <what users can do afterwards>

The assistant first drafts the requirement in the chat. It creates the branch and worktree only after you approve the draft, and the worktree starts with just the requirements folder, so a large repository is not copied for an idea you may drop.

The assistant links the work to a requirement, plans, writes the test first, implements, runs xaden check, and runs a security review when the change touches input, logins, data, files, the network or dependencies. It updates your documentation and changelog and commits with a Refs: REQ-nnn trailer that names the requirement.

You see:

• a commit per coherent step, in Conventional Commit form (feat: ..., fix: ...);
• a completion report at the end: the checks that ran, the checks that were skipped, unresolved findings, and the evidence for each acceptance criterion.

When the checks fail

Fix the finding; do not silence a rule without a one-line reason. A commit that cites a requirement that does not exist is rejected, and so is a feat commit without a Refs: line. Loosening a linter setting or the mode of the checks is an approval point.

Other tasks

Claude Code, GitHub Copilot and Mistral Vibe have a slash command for each prompt (Codex CLI a $name skill) when your team chose them; other assistants run the xaden prompt command.

Changed your mind during a feature? Say so; the assistant updates the requirement first and then the code.

Next

Release a version.