flagship-docs-create

Generate contracts-first documentation packages covering vision, requirements, architecture, and testing strategies.

Updated Aug 27, 2026

Search Tags:#project management #architecture #documentation #requirements #traceability #contracts-first

Ready to run

npx skills add https://github.com/AmirTlinov/magray-marketplace --skill flagship-docs-create

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flagship-docs-create
Source: https://github.com/AmirTlinov/magray-marketplace/tree/main/flagship-team/skills/flagship-docs-create
Command: npx skills add https://github.com/AmirTlinov/magray-marketplace --skill flagship-docs-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating comprehensive documentation from scratch for a new idea or project, ensuring all necessary components for end-to-end implementation are covered.

Core Features & Use Cases

Generates a complete set of documentation files including vision, requirements, architecture, and testing strategies.
Ensures full traceability from requirements to contracts, tests, and gates.
Supports versioned domain contracts and a clear release/rollback strategy.
Use Case: Kickstart a new software project by generating all foundational documentation required for development and deployment.

Quick Start

Use the flagship-docs-create skill to generate a full documentation package for a new project based on the provided outcome and scope.

Frequently Asked Questions about flagship-docs-create

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

FAQPage Schema

How do I generate full project documentation from scratch for a new software idea?▼

To generate full project documentation, define your project outcome and scope, then use a contracts-first approach to produce vision, requirements, architecture, invariants, NFRs, risk registers, and testing strategies.

What is a contracts-first documentation approach and when do I need it?▼

A contracts-first documentation approach generates versioned domain contracts before implementation, ensuring requirements are testable and maintaining full traceability from requirements to tests and release gates.

How do I ensure traceability from requirements to tests and deployment gates?▼

Traceability from requirements to tests is maintained by generating a comprehensive traceability matrix that links vision, requirements, architecture, and testing strategies to release and rollback plans.

Can I generate architecture and risk registers for new projects without existing documentation?▼

Yes, you can generate architecture, risk registers, and non-functional requirements for new projects without existing documentation by providing the initial outcome and scope to establish foundational files.

What's the best way to create a release and rollback strategy alongside project requirements?▼

The best way to create a release and rollback strategy alongside requirements is to generate a complete documentation package that includes testing strategies and plan slices for end-to-end implementation.

Do I need existing architecture files to generate invariants and non-functional requirements?▼

No, you do not need existing architecture files to generate invariants and non-functional requirements; the documentation package can be created from scratch based solely on the provided outcome and scope.