f2s-doc-final

Convert PDF or Markdown documents into a standardized final-draft specification template.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw PDF or Markdown documents often lack a consistent structure, making them hard to route into a project knowledge base. This Skill restructures them into a standardized final-draft format with sections like core concepts, business rules, and key flows, ready for downstream knowledge-base synchronization. ## Core Features & Use Cases - Markdown Conversion: Reads an existing .md file and reorganizes it into the final-draft template structure with required second-level headings. - Two-Step PDF Pipeline: Extracts PDF text into a draft Markdown file first, then converts the confirmed draft into the final template format after user review. - Knowledge Base Integration: Writes outputs to .Knowledge/stock-docs/ with _初稿 (draft) or _终稿 (final) suffixes so the f2s-kb-build skill can sync topics, index, and manifest. - Use Case: You receive a 40-page PDF technical design document. Run this Skill to produce a draft, review it, then run it again to generate a structured final document with concept tables, business rules, and key flows for your project knowledge base. ## Quick Start Run f2s-doc-final with the path to your PDF or Markdown file, for example: f2s-doc-final .Knowledge/stock-docs/design.pdf, then confirm the draft and run it again on the generated draft file to produce the final version.

Frequently Asked Questions about f2s-doc-final

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

FAQPage Schema
How do I convert a PDF into a structured Markdown specification?▼

Pass the PDF path as the first argument to f2s-doc-final. It extracts the text into a draft Markdown file in .Knowledge/stock-docs/, then after you review it, run the skill again on the draft path to produce the final templated version.

How do I reformat an existing Markdown document into a standard template?▼

Pass the .md file path as the first argument. The skill reads the content, reorganizes it into sections like core concepts, business rules, and key flows, and writes the result to .Knowledge/stock-docs/ with a _终稿 (final) suffix.

Can I specify a custom output path for the converted document?▼

Yes, provide a second argument after the input file path to override the default output location. Without it, outputs go to .Knowledge/stock-docs/ with a name derived from the document title.

What happens if the PDF cannot be parsed directly?▼

If the environment cannot extract PDF text, the skill asks you to manually convert the PDF content into a .md file under .Knowledge/stock-docs/ and then run the skill on that Markdown file instead.

Is the final-draft template mandatory when converting documents?▼

No, the template at .Knowledge/template/终稿模版.md is only a structural hint. The skill recommends keeping core concepts, business rules, and key flows sections, but other sections can be added or removed based on the source content.