f2s-doc-pdf

Convert PDF technical design documents into Markdown files stored in req-docs.

48|6|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/double-coding-lab/Flow2Spec --skill f2s-doc-pdf-double-coding-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: f2s-doc-pdf
Source: https://github.com/double-coding-lab/Flow2Spec/tree/main/.cursor/skills/f2s-doc-pdf
Command: npx skills add https://github.com/double-coding-lab/Flow2Spec --skill f2s-doc-pdf-double-coding-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical design documents often arrive as PDFs that AI coding agents cannot easily read or act on, and embedded flowcharts lose their logic when copied as plain text. This Skill converts a PDF design document into a structured Markdown file saved under .Knowledge/req-docs/, and optionally captures flowchart logic as written steps so the design can later drive code implementation. ## Core Features & Use Cases - PDF to Markdown Conversion: Reads a user-supplied PDF path, extracts text while preserving tables, sections, lists, and code blocks, and saves the result as .Knowledge/req-docs/<name>.md. - Flowchart Supplementation: Prompts the user to provide flowchart images or written step descriptions, then appends a structured "流程说明" (process description) section to the generated Markdown. - Optional Sub-Agent Splitting: For large PDFs (over 50 pages or roughly 5MB of text), a sub-agent can produce the first Markdown draft while the main agent handles user follow-up questions. - Use Case: You receive a 30-page technical design PDF for a new feature. Run this Skill to convert it into Markdown, paste the flowchart screenshots into the chat, and get a complete implementation-ready document that the implement-tech-design rule can consume. ## Quick Start Convert the PDF at ~/Downloads/tech-design.pdf into Markdown and save it to .Knowledge/req-docs/, then help me add the flowchart steps.

Frequently Asked Questions about f2s-doc-pdf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a PDF technical design document to Markdown?▼

Provide the local path to your PDF file as the argument when invoking the Skill. It reads the PDF, extracts text while preserving tables, sections, lists, and code blocks, and saves the result as a Markdown file in .Knowledge/req-docs/.

How to preserve flowcharts when converting PDF to Markdown?▼

Flowcharts embedded in PDFs cannot be parsed directly into steps and branches. The Skill asks you to either send the flowchart as an image in the chat or describe the steps in text, then appends them as a process description section in the Markdown file.

Where does the converted Markdown file get saved?▼

Converted files are saved to .Knowledge/req-docs/<name>.md, where the name is the original PDF filename with the .pdf extension replaced by .md. The directory is created automatically if it does not exist.

Can large PDF files be converted to Markdown?▼

Yes, but PDFs over 50 pages or roughly 5MB of text trigger an optional sub-agent mode when subAgent is enabled. The sub-agent produces only the first Markdown draft, while the main agent handles user questions and flowchart writing.

Does this Skill implement the code from the design document?▼

No, it only handles PDF to Markdown conversion and optional flow description completion. After conversion, you provide the generated Markdown path in the conversation and the separate implement-tech-design rule executes the code implementation.