Break down technical initiatives into planning artifacts and structured requirements.
npx skills add https://github.com/infraspecdev/tesseract --skill plan-docs
Please help me install this Agent Skill. Skill: plan-docs Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/general/plan-docs Command: npx skills add https://github.com/infraspecdev/tesseract --skill plan-docs
This Skill turns a vague project idea into a complete execution package, removing the manual work of translating scope into stories, milestones, and technical requirements.
It helps you create detailed project plans, architecture-ready technical requirements, and milestone roadmaps that are structured for engineering execution and review.
Use it when you need to break a phase into testable stories, write decision-ready documentation, or generate a plan that links requirements to implementation work.
Use the plan-docs skill to turn this feature into a complete milestone plan with stories, acceptance criteria, a TRD, and rendered HTML outputs.
High-intent search queries and answers about installing and using this skill.
You can break down a technical initiative by generating structured planning artifacts that include milestone roadmaps, testable stories with acceptance criteria, and a validated plan sidecar for execution.
A TRD is a 14-section Technical Requirements Document that structures architecture decisions and technical requirements into markdown and HTML outputs, ensuring engineering teams have decision-ready documentation.
Yes, you can generate milestone roadmaps with low-level design (LLD) linkage, producing design references and structured requirements specifically for backend or infrastructure work.
Yes, the planning process produces validated plan sidecars and rendered HTML outputs designed to make documentation decision-ready and structured for engineering plan reviews.
The best way is to decompose the technical initiative into structured requirements, which generates testable stories with clear acceptance criteria and milestone linkage for implementation.
Automated story decomposition should not be used when the project idea is too vague to define scope, as the process requires translating defined scope into structured requirements and executable artifacts.
dtsongTransform natural language project descriptions into structured engagement briefs.
simon-downesExecute approved implementation plans through milestone-based workflows with progress tracking.
anis-marrouchiImplement the next unpassed user story from .ralf/prd.json within a Ralf loop.
Pear-CommerceAdd sequential integer phases to the active GSD milestone roadmap.
