Transform high-level feature descriptions into structured specs with acceptance criteria.
npx skills add https://github.com/Docaari/GrindfyManager --skill pm-spec-docaari
Please help me install this Agent Skill. Skill: pm-spec Source: https://github.com/Docaari/GrindfyManager/tree/main/.claude/skills/pm-spec Command: npx skills add https://github.com/Docaari/GrindfyManager --skill pm-spec-docaari
Gera especificaƧƵes estruturadas de features a partir de descriƧƵes de alto nĆvel. Transforma ideias vagas em documentos acionĆ”veis que outros agentes consomem. Invoque SEMPRE ao iniciar qualquer feature nova, quando o usuĆ”rio descrever uma funcionalidade que precisa ser planejada, quando alguĆ©m disser 'quero criar', 'preciso de uma feature', vamos construir', ou qualquer variaĆ§Ć£o de pedido de nova funcionalidade. TambĆ©m invoque quando precisar decompor um requisito grande em partes menores. NĆO use para tarefas de implementaĆ§Ć£o, review de cĆ³digo ou deploy.
Descreva brevemente a feature desejada para que o PM-Spec inicie a geraĆ§Ć£o da especificaĆ§Ć£o.
High-intent search queries and answers about installing and using this skill.
To turn vague ideas into actionable specs, you provide a high-level feature description to trigger a guided interview that captures context, decomposes requirements, and outputs a structured document with acceptance criteria and test scenarios.
Decomposing large requirements into testable sub-features involves conducting a contextual interview to break down the initial description, ensuring each sub-item remains independent and clearly defined before generating the final specification.
Writing a feature specification with acceptance criteria and test scenarios requires gathering high-level descriptions and objectives, then structuring that context into a complete document formatted specifically for AI agents to consume.
This specification tool does not propose code or architectural choices. It strictly focuses on capturing context, decomposing requirements, and defining acceptance criteria and test scenarios for your features.
You should use a requirements decomposition workflow when initiating any new feature or when needing to break down a large request into smaller parts, rather than for tasks involving actual code implementation, code review, or deployment.
TalonT-OrgDecompose high-level tasks into structured, independently plannable requirements.
thegeronimoDesignescribes acceptance and integration test proposals from frozen specs or ExecPlans for downstream teams.
cslsoftwaresConverts PRDs into SPEC.json and SPEC.md with tasks and acceptance criteria.
iCesofTApply Behavior-Driven Development patterns with Given-When-Then scenarios and feature files.
