f2s-doc-milestone

Generates project milestone documents from requirement docs, git history, task records, and knowledge base topics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing an accurate project milestone document requires manually cross-referencing requirement docs, git tags, task records, and knowledge base topics, which is slow and error-prone. This Skill automates that synthesis into a single verified milestone document. ## Core Features & Use Cases - Four-source collection: Gathers evidence from .Knowledge/req-docs/, git log and tags, .task/ records, and knowledge base topic semantics before writing anything. - Fixed sub-agent orchestration: A sub agent drafts the milestone from a template while the main agent verifies coverage, ordering, and stage granularity, regardless of project config switches. - Semantic scoping: Accepts an optional natural-language scope (e.g., a single feature or the whole project) and writes the result to .Knowledge/stock-docs/<scope>里程碑.md. - Use Case: After shipping several releases, ask the agent to generate the project milestone; it produces a reverse-chronological stage overview with only verifiable feature deliveries and a "to be confirmed" section for gaps. ## Quick Start Ask the agent to run f2s-doc-milestone to generate the milestone document for the entire project or a named feature scope.

Frequently Asked Questions about f2s-doc-milestone

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

FAQPage Schema
How do I generate a project milestone document with an AI coding agent?▼

Invoke the f2s-doc-milestone command, optionally followed by a natural-language scope such as a feature name. The skill collects requirement docs, git tags, task records, and knowledge base topics, then writes a milestone Markdown file to .Knowledge/stock-docs/.

What sources does milestone generation use as evidence?▼

It uses four sources: requirement docs under .Knowledge/req-docs/, git log and tags plus package.json versions, task records under .task/, and knowledge base topic semantics from manifest-routing.json and index.md. Stages without evidence in these sources are not written.

Can I generate a milestone for only one feature or module?▼

Yes. Append a semantic scope after the command, such as a feature or module name, and the four sources are filtered by keyword, path, and date. The output file is named after that scope with the milestone suffix.

Does the milestone skill follow the project's sub-agent configuration?▼

No. This skill uses a fixed orchestration where a sub agent drafts and the main agent verifies, regardless of the subAgent or switchAgentVerification settings in flow2spec.config.json. The config file is still read to satisfy prerequisite checks.

What happens if a similar milestone file already exists?▼

The main agent lists existing milestone files in stock-docs and asks the user before writing. You can choose to overwrite the existing file or generate a new one with a date-suffixed or custom name; silent overwrites are forbidden.

Why are testing or deployment phases missing from my milestone?▼

The skill only records stages with verifiable feature or capability deliveries. Pure integration testing, UAT, acceptance, or environment-only work is merged into the related feature stage or omitted, with gaps noted in the to-be-confirmed section.