From maister
Initializes .maister/docs/ with codebase analysis, documentation generation, standards selection, and coding standards discovery.
npx claudepluginhub skillpanel/maister --plugin maisterThis skill uses the workspace's default tool permissions.
Initialize `.maister/docs/` with intelligent project analysis and meaningful documentation generation based on actual codebase inspection.
Initializes .maister/docs/ AI SDLC framework via pre-flight checks, project codebase analysis, standards selection, documentation generation, and validation.
Manages .maister/docs/ directory: file operations, INDEX.md generation, CLAUDE.md integration for project docs and standards. Internal; invoked by maister:init, standards-update, standards-discover.
Initializes Quaestor in projects with auto-framework detection, parallel architecture/security analysis, customized doc generation, user validation, and setup completion.
Share bugs, ideas, or general feedback.
Initialize .maister/docs/ with intelligent project analysis and meaningful documentation generation based on actual codebase inspection.
NOTE: This skill invokes other skills and subagents at specific phases. Use the Task tool with docs-operator subagent (subagent_type: maister:docs-operator) for all docs-manager operations, and Task tool for project-analyzer. Use the Skill tool only for standards-discover (Phase 8, last phase). The Task tool returns control to this skill after completion; the Skill tool does not.
| Phase | Subject | activeForm |
|---|---|---|
| 1 | Pre-flight checks | Running pre-flight checks |
| 2 | Analyze project codebase | Analyzing project codebase |
| 3 | Present findings & gather context | Gathering project context |
| 4 | Select standards to initialize | Selecting standards |
| 5 | Initialize documentation structure | Initializing documentation |
| 6 | Generate project documentation | Generating project documentation |
| 7 | Validate | Validating initialization |
| 8 | Discover coding standards | Discovering coding standards |
Task Tracking: Before Phase 1, use TaskCreate for all phases (pending), then set sequential dependencies with TaskUpdate addBlockedBy. At each phase: TaskUpdate to in_progress → execute → TaskUpdate to completed. If skipped (e.g., user selects "Update existing"), mark skipped phases as completed with metadata: {skipped: true}.
If --standards-from=PATH is provided:
PATH/.maister/docs/standards/ exists. If not, inform the user and stop — the specified project doesn't have maister standards initialized.Check if .maister/ directory already exists.
If exists, use AskUserQuestion:
.maister.backup-$(date +%Y%m%d-%H%M%S)/ using Bash toolInvoke project-analyzer subagent via the Task tool.
Wait for completion. Store analysis results for use in Phases 3 and 6.
Step 1: Present analysis results to the user (project type, primary language/framework, architecture, tech stack, conventions, strengths/opportunities).
Step 2: Use AskUserQuestion to confirm analysis accuracy. If corrections needed, collect them.
Step 3: Gather additional context via AskUserQuestion (adapt to project type):
Step 4: Ask which project documentation to generate using AskUserQuestion (multi-select):
Smart defaults based on projectArchitectureType:
Store selections for Phase 6.
Before presenting options, explain to the user:
--standards-from was provided, standards come from the referenced project. Otherwise, the plugin includes generic built-in standards. Either way, they serve as a starting point and can be fully customized or extended later.Determine available categories:
--standards-from was provided: Scan PATH/.maister/docs/standards/*/ to discover all available categories from the external project (may include custom categories beyond the baseline global/frontend/backend/testing).Calculate smart defaults based on analysis:
Also scan .maister/docs/standards/*/ for any existing custom categories to include.
Show smart defaults summary (noting the source: external project or built-in), then use AskUserQuestion:
Custom categories: if user adds a new category, create the directory and include it in the selection.
Store selection for Phase 5.
Invoke docs-operator subagent via Task tool (subagent_type: maister:docs-operator) with prompt:
"Initialize documentation structure. Standards selection: [array from Phase 4]. [If --standards-from was provided: Standards source path: [resolved path]/.maister/docs/standards/. Copy standards from this external path instead of built-in defaults.] Only copy selected standard categories. Do NOT copy project templates — only create the project/ directory. Project documentation will be generated in Phase 6 with real content from project analysis. Create placeholder sections in INDEX.md for skipped categories."
Wait for docs-operator to complete, then immediately proceed to Phase 6.
IMPORTANT: Only generate docs selected in Phase 3.
For each selected doc type, read the corresponding reference template:
references/vision-templates.md, select template by project type (new/existing/legacy)references/roadmap-templates.md, select template by project typereferences/tech-stack-template.mdreferences/architecture-template.mdFill templates using:
Write each file to .maister/docs/project/.
Step 1: Invoke docs-operator subagent via Task tool (subagent_type: maister:docs-operator) with prompt:
"Regenerate INDEX.md to include all newly created project documentation. Then verify CLAUDE.md is properly integrated with .maister/docs/ documentation."
Wait for docs-operator to complete, then immediately continue with Step 2.
Step 2: Run validation checks:
Step 3: Display comprehensive summary:
/maister:workInvoke the standards-discover skill via Skill tool with --scope=full to automatically discover coding standards from the project's config files, source code patterns, documentation, and external sources.
"Run standards discovery with --scope=full. This is being invoked as part of project initialization."
The standards-discover skill handles its own user interaction (presenting findings by confidence tier, asking for approval). Let it run its full workflow — this is the last phase of init, so context handoff is fine here.
After completion, display a brief summary of how many standards were discovered and applied.
.maister/docs/ creation fails: check permissions, suggest manual creation