skf-create-stack-skill

Assemble a stack skill from project manifests and architecture documents.

91|9|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/armelhbobdad/bmad-module-skill-forge --skill skf-create-stack-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skf-create-stack-skill
Source: https://github.com/armelhbobdad/bmad-module-skill-forge/tree/main/src/skf-create-stack-skill
Command: npx skills add https://github.com/armelhbobdad/bmad-module-skill-forge --skill skf-create-stack-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Consolidates the process of turning project manifests, architecture documents, and pre-generated skills into a single, verifiable stack skill that can be evolved and deployed reproducibly.

Core Features & Use Cases

  • Code-mode analysis: analyzes dependency manifests to derive libraries and integration patterns from real codebases.
  • Compose-mode synthesis: builds a stack skill by combining existing skills with architecture documentation when code does not exist.
  • Provenance-driven artifacts: ensures every finding traces back to file:line citations or architecture references for auditability.
  • Workflow orchestration: coordinates manifest detection, extraction, integration detection, stacking, and artifact generation in a repeatable pipeline.

Quick Start

Provide your project_name and optional architecture document path; SKF will generate a complete {project_name}-stack with all required references, catalogs, and workspace artifacts.

Frequently Asked Questions about skf-create-stack-skill

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

FAQPage Schema
How do I automate stack skill creation from project manifests and architecture documents?

Stack skill creation is automated by orchestrating manifest detection, extraction, and integration inference to assemble a verifiable stack skill with provenance mapping. This skill synthesizes project libraries and architecture docs into a reproducible deployable artifact.

What is the difference between code-mode and compose-mode for deriving integration patterns?

Code-mode analyzes dependency manifests to derive libraries and integration patterns from existing codebases, whereas compose-mode synthesizes a stack skill by combining existing skills with architecture documentation when source code is unavailable.

How do I ensure provenance and auditability when generating workspace artifacts from dependency manifests?

Provenance and auditability are ensured by mapping every finding back to file:line citations or architecture references. This skill coordinates artifact staging to guarantee that all derived references and catalogs are fully traceable for audits.

Can I build a stack skill from architecture documentation if my project has no existing codebase?

You can build a stack skill without code using compose-mode synthesis. This workflow combines your existing pre-generated skills and architecture documents to infer integrations and generate the complete stack artifact.

What inputs do I need to provide to generate a complete stack with catalogs and workspace artifacts?

To generate a complete stack, provide your project_name and an optional architecture document path. The workflow then detects dependency manifests, extracts libraries, and stages all required references and catalogs automatically.