Feature Ship Workflow FAQs

Question 1

Does this skill update my project dashboard?

Accepted Answer

Yes, creating the 'shipped.md' file triggers a hook that automatically regenerates the DASHBOARD.md file to reflect the new completion status.

Question 2

How does it track feature completion status?

Accepted Answer

Status is determined by file presence in the docs/features/ directory. When the feature-ship skill creates a 'shipped.md' file, the feature is automatically moved to completed status.

Question 3

Does Feature Ship support different project sizes?

Accepted Answer

Yes, the workflow scales its intensity based on effort. Small tasks run basic audits and tests, while Medium/Large tasks invoke specialized security and QA agents.

Question 4

What are the quality gates in the Feature Ship workflow?

Accepted Answer

The workflow includes six phases: Pre-flight checks, Security Review (OWASP/CVE scans), QA Validation (test coverage), Final Verification (lint/build/test), Documentation (shipped.md), and a final Summary.

Question 5

What happens if security issues are found during the ship process?

Accepted Answer

The workflow is designed to block completion if Critical or High-level vulnerabilities are detected, ensuring that quality and security are never optional.

Feature Ship Workflow

主要功能

使用场景

Feature Ship Workflow

主要功能

使用场景