Loading...
Loading...
Found 116 Skills
Guide for creating and maintaining project documentation (README, guides, API specs). Emphasizes doc/code synchronization, consistency checks, and use of the docs-excellence-architect subagent.
Initialize or update project documentation. Use when setting up docs for a new project (`--init`) or syncing docs to current codebase and architecture changes (`--update`).
Project documentation structure creation assistant. Acting as a senior product manager, it gains in-depth understanding of project requirements through multiple rounds of conversations, analyzes rationality and provides best practice suggestions, and finally generates a complete technical documentation system.
Generate a custom checklist for the current feature based on user requirements.
Project documentation that stays alive. Read before starting work, update after finishing. Covers project setup, specs, architecture diagrams, and execution plans. Use when starting a project, writing a spec, checking existing docs, updating docs after changes, or when someone says "set up docs", "create a plan", "audit docs", or "init project".
Generate various types of documents based on the current project/code, supporting four types: thesis chapters, project sorting, key issues, and resume project descriptions. Use this when the user mentions generating thesis chapters, project sorting, technical difficulties, or resume project descriptions.
Initialize .chalk folder — analyze a repo and capture its architecture, coding style, tech stack, design assets, and project identity into chalk.json and structured docs
Create a stakeholder update when the user asks to write a status update, send a project update, prepare an executive summary, or draft a BLUF update
Creates structured development plans with phased task breakdowns, requirements, and QA checklists. Use when the user explicitly asks to create a dev plan, development plan, or document development requirements.
Execute the implementation planning workflow and generate design artifacts using the plan template. Trigger phrase: "speckit plan".
Record a business artifact (.oh/ metis, signal, guardrail, or outcome update). Use when capturing learnings, measurements, constraints, or updating outcome status.
Guide for following MassGen's release documentation workflow. This skill should be used when preparing release documentation, updating changelogs, writing case studies, or maintaining project documentation across releases.