build_functional_requirementsLABSCO SUMMARY
A development lifecycle an agent can actually follow.
Each document narrows the one above it until a subtask is small enough to be a single commit, and execution stops for review before committing - so the plan stays legible to you instead of disappearing into one long generation.
What it is
An MCP server that gives an agent a fixed development workflow, with a Rails leaning. It collects functional requirements, turns them into a PRD, splits each feature into a pull-request-sized FRD, then breaks that into a task design document where every subtask is one commit. Documents and task state are written into .cursor/scratch/ in the repository.
What you get
- Project requirements collected through a structured interview - purpose, users, capabilities, workflows, edge cases
- A PRD generated from those requirements, broken into features and user stories
- A feature requirements document sized to a single pull request
- An implementation plan whose subtasks map one-to-one onto commits
- Architecture documentation for the project
- Those subtasks set up as trackable work
- One task executed at a time, pausing for review before the commit
Requirements
An MCP client with an mcp.json, and a repository the server can write to - the documents, the task list and the progress notes all land in .cursor/scratch/. For a system you already understand, skip the first three documents and start at the task design step.
Setup effort
One command — docker run -i --rm cestbalez/railagent:latest
USE CASES
01
Starting a new app from a rough idea
The requirements interview asks for the things you would otherwise discover late, and the PRD comes out of the answers.
02
Splitting a feature that is too big to review
The feature document is sized to one pull request, and the task design breaks it into commits.
03
Adding to a system you already understand
Skip straight to the implementation plan and set its subtasks up as work.
04
Keeping an agent from committing before you have looked
Each task runs on its own and waits at a review checkpoint.
05
Writing down an architecture nobody documented
Generate the architecture document from the project as it stands.
7 tools
Listed in project docs. Your client may show a different list.
build_prdbuild_frdbuild_tddbuild_architectureinitialize_taskexecute_taskBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
docker on PATH
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"Railagent": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"cestbalez/railagent:latest"
]
}
}
}docker
TERMINAL
docker run -i --rm cestbalez/railagent:latest
