plan-stack

Scan project build files and source layout to generate stack configuration entries.

9|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/mark22013333/crew --skill plan-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-stack
Source: https://github.com/mark22013333/crew/tree/main/plugins/feature-workflow/skills/plan-stack
Command: npx skills add https://github.com/mark22013333/crew --skill plan-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

透過自動偵測與互動式設定,協助團隊快速建立並維護專案技術棧的範本掃描規則,減少手動配置成本。

Core Features & Use Cases

  • 自動偵測專案分層結構,辨識框架、ORM 與資料庫,並產生範本掃描規則。
  • 互動與自動模式切換,將規則寫入 stacks/{id}.md,並可覆蓋或更新既有設定。
  • 支援跨語言與多模組專案,適用於典型企業架構與非標準分層。

Quick Start

直接執行 /plan-stack 開始偵測並建立或更新技術棧檔案。

Frequently Asked Questions about plan-stack

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

FAQPage Schema
How do I auto-detect a tech stack for a multi-language project?

To auto-detect a tech stack for a multi-language project, this tool scans your project structure and analyzes build files like pom.xml and build.gradle to identify frameworks, ORMs, and databases, then generates tailored scanning rules.

What do I need to configure before scanning project structures for tech stacks?

Before scanning project structures for tech stacks, you need a CLAUDE.md file in place and project read access to your build files so the scanner can accurately analyze your source layout and generate configuration entries.

How does template scanning rule generation work for multi-module architectures?

Template scanning rule generation for multi-module architectures works by analyzing your build files and source layout to produce stacks/{id}.md entries, guiding rule creation while validating that IDs do not clash with built-in stacks.

Can I update existing tech stack configurations without overwriting my custom rules?

Yes, you can update existing tech stack configurations without losing custom rules by switching between interactive and automatic modes, which allows you to append or modify stacks/{id}.md files rather than blindly overwriting them.

Why do my generated stack IDs conflict with built-in stacks during configuration writing?

Generated stack IDs conflict with built-in stacks during configuration writing when names overlap, which is why the tool validates that custom IDs do not clash with built-in stacks before writing any template scanning rules to disk.