Recursive Implement
Build a project using recursive multi-agent development with TDD
Install
$ agentstack add skill-jartan-llc-grimoire-recursive-implement ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jartan-llc-grimoire-recursive-implement) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Recursive Implement
Build a project (or feature) using waves of parallel nested subagents with TDD at every level.
Process
1. Gather Context
Collect everything the orchestrator needs into a single prompt:
- From the user's request: the project description, issue number, or plan file path
- If issue number: fetch the issue body with
gh issue viewand include it - From conversation: if the user discussed requirements, architecture decisions, constraints, or preferences in this session, summarize the relevant parts
- From existing project: if working in an existing codebase, note the language, test framework, key conventions, and any relevant file paths
2. Launch Orchestrator
Spawn a recursive-orchestrator. The prompt should contain:
[Project description or plan file path]
[Conversation context if any -- requirements, constraints, decisions made]
[Existing project context if any -- language, conventions, key files]
Working directory: [cwd]3. Report Results
Relay the orchestrator's final report to the user.
Failure Recovery
If the orchestrator reports a failure, present the context to the user. On re-run:
- The wave plan persists in
.claude/workspace/-- pass the file path to skip re-planning - Completed source files and tests remain on disk -- the orchestrator can build on them
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jartan-LLC
- Source: Jartan-LLC/grimoire
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.