Convert unstructured notes and chats into a formal requirements document.
npx skills add https://github.com/samdae/archflow --skill spec-samdae
Please help me install this Agent Skill. Skill: Spec Source: https://github.com/samdae/archflow/tree/main/skills/spec Command: npx skills add https://github.com/samdae/archflow --skill spec-samdae
The Spec skill transforms scattered materials into structured, testable requirements documents, establishing a single source of truth for product initiatives.
Launch the Spec skill, provide the input material (Notion/Markdown or chat history), and name your service. The tool will produce a standardized docs/{serviceName}/spec.md and guide you through the Q&A to finalize the requirements.
High-intent search queries and answers about installing and using this skill.
To turn unstructured notes into a requirements document, provide scattered Markdown or Notion inputs to trigger an iterative Q&A refinement loop that resolves ambiguities and outputs a structured specification.
Yes, you can generate acceptance criteria and traceable IDs from chat history by feeding the conversations as input material, which the system converts into a standardized specification format with unique identifiers.
The requirements generation process supports both Notion and Markdown inputs, converting them into a consistent specification format ready for architecture and design handoffs.
The best way to resolve ambiguities when writing software specifications is using an iterative Q&A loop that refines scattered inspiration into clear requirements with testable acceptance criteria.
You create a standardized spec.md file by naming your service and providing input materials, which automatically generates the formal requirements document at the output location docs/{serviceName}/spec.md.
VegaStackSynchronize local markdown files with Notion pages bi-directionally.
tmdgusyaOrchestrate multi-agent workflows to produce SPEC.md and IMPLEMENTATION_PLAN.md documents.
AhmedElhadareySynchronize stale business documentation when track decisions change.
lionbenjaminDraft product specifications with problem, goals, user stories, and acceptance criteria.
