Convert feature specifications into implementation plans with TDD and governance requirements.
npx skills add https://github.com/ArvorCo/Relentless --skill plan-arvorco
Please help me install this Agent Skill. Skill: plan Source: https://github.com/ArvorCo/Relentless/tree/main/.claude/skills/plan Command: npx skills add https://github.com/ArvorCo/Relentless --skill plan-arvorco
Relentless teams often struggle to convert feature specifications into structured, verifiable implementation plans. This Skill automates the translation, ensuring consistent planning, documentation, and alignment with governance requirements.
Run the Relentless plan command against the latest feature spec to produce relentless/features/NNN-feature/plan.md.
High-intent search queries and answers about installing and using this skill.
To convert a feature specification into an implementation plan, run the Relentless plan command against your spec.md file. It auto-generates a structured plan.md containing the technical overview, data models, API contracts, and implementation strategy.
Automated planning enforces Test-Driven Development by embedding complete test specifications and quality gates directly into the generated plan. This ensures TDD requirements are carried forward from the spec to guide subsequent task creation and implementation.
Yes, you can use this to ensure governance compliance in your technical plan. The generation process automatically enforces routing preferences and constitution compliance, carrying these critical governance requirements forward into the final plan output.
The best way to generate data models and API contracts from a feature spec is using an automated planning tool. It translates relentless spec files into ready-to-submit plans, accelerating software delivery by structuring technical overviews and implementation strategies automatically.
Yes, the plan generation works without dependencies in the Relentless workflow. It operates independently to translate feature specs into structured plans, applying TDD and governance rules across the spec to plan to tasks sequence.
You need to generate a technical plan from a specification file when your team struggles to convert feature specs into structured, verifiable implementation plans. It ensures consistent planning, documentation, and alignment with governance requirements to accelerate software delivery.
Wike-CHIGenerate daily report drafts in Markdown from date, highlights, and blockers.
GenEducationExecutes approved software stories with test-driven code delivery.
ArvorCoGenerate Markdown validation checklists from spec, plan, and tasks documents.
aniruddh2003Generate technical design documents from feature specifications.
