technical-writer
No SKILL.md available for this skill.
View on GitHubMore from raffaelecamanzo/skills
marp-deck-planner
Plan a MARP presentation from a high-level deck definition (sections, key messages, constraints). Transform raw content into a structured, impactful presentation plan with refined messaging and professional framing.
27business-analyst
Analyze a user request document and produce a Functional Requirements Specification (FRS) and User Acceptance Test (UAT) cases. Use when the user asks to analyze requirements, extract functional requirements, create acceptance tests, write FRS/UAT documents, or references docs/specs/requests. Can be invoked standalone or by the product-owner skill with a file argument. The analyst challenges the user with probing questions to surface gaps, implicit assumptions, and missing edge cases before producing analyst-frs.md and analyst-UAT.md at docs/specs/.
7product-owner
Run the full requirements workflow — collaborative scoping, functional analysis (BA), non-functional analysis (technical writer), cross-reference review, and unified SRS generation. Use when the user asks for a "full specification", "SRS", "complete requirements workflow", or "run the product-owner". Orchestrates the business-analyst and technical-writer skills sequentially, then cross-references their outputs to detect conflicts and gaps before producing docs/specs/software-spec.md.
7journal-creator
Read the SRS, architecture, and frontend-design specs to produce a comprehensive, dependency-ordered journal of user and technical stories at docs/planning/journal.md. Use when the user asks to "create a journal", "generate stories", "plan the backlog", "create a story map", or "break down the specs into stories". Can be invoked standalone after the product-owner and design-coordinator workflows complete, or with explicit file paths.
4md2pdf
>
3