swe-init

Gather company, product, and architecture details into Markdown context files.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/MmtBkn/swe --skill swe-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swe-init
Source: https://github.com/MmtBkn/swe/tree/main/swe-init
Command: npx skills add https://github.com/MmtBkn/swe --skill swe-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill establishes foundational context for a software project by gathering and organizing information about the company, product, and architecture, making it readily available for subsequent development tasks.

Core Features & Use Cases

  • Contextual Briefs: Creates structured Markdown files for company, product, and architecture details.
  • Information Gathering: Leverages web searches and internal knowledge bases (if accessible) to collect relevant data.
  • Use Case: Before starting a new feature, use swe-init to ensure all necessary background information about the company's mission, the product's value proposition, and the existing architecture is documented and accessible.

Quick Start

Use swe-init to initialize context for the 'Acme Corp' product 'WidgetPro'.

Frequently Asked Questions about swe-init

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

FAQPage Schema
How do I create project context documentation for onboarding AI development workflows?

Project context documentation is generated by scanning local repositories and gathering company, product, and architecture information. The tool creates structured Markdown files in `.swe/context/` to provide accessible project background for development workflows.

What is the best way to document software architecture and company background for a new repository?

Documenting software architecture and company background is done by scanning local repositories and leveraging web searches or knowledge bases. This gathers product and architecture details into structured Markdown files for comprehensive project context.

How do I generate a knowledge base from local repositories and internal documentation?

To generate a knowledge base from local repositories, the tool scans the codebase and queries internal knowledge bases or the web. It organizes the collected company, product, and architecture information into structured Markdown context files.

Does this project setup tool require any external dependencies to build repo context?

No external dependencies are required to build repo context with this project setup tool. It operates independently to scan repositories and utilize web searches or internal knowledge bases for gathering information into Markdown files.

Can I use gathered company and product information to structure development context for my team?

Yes, gathered company and product information can be used to structure development context. The tool creates contextual briefs as structured Markdown files, making background information readily accessible for subsequent team development tasks.

When do I need to initialize structured context files for a software development project?

You need to initialize structured context files before starting new features or AI-driven development workflows. This ensures all necessary background information about the company, product, and existing architecture is documented and accessible.