Astro-Noctum

Use this skill EVERY TIME an aphorism is added, validated, corrected, or imported into the Bazodiac collection under knowledge/bazodiaac-brain/aphorisms/. Verifies source attribution against trusted sources, refines DE and EN translations against the semantic core of the original, enforces the bilingual aphorism schema exactly (YAML frontmatter, body sections, blockquote, controlled vocabulary, attribution status), recomputes word counts, and either delivers a clean .md file or sorts the entry out with a reasoned verdict when attribution is unclear or rights are fraught. Triggers on phrases like "neuer Aphorismus", "Aphorismus hinzufügen", "kurate diesen Spruch", "validiere dieses Zitat", "Block 2 / Block 3", "Aphorismus-Eintrag", "ist dieser Spruch von …", "passt die Zuschreibung". Manual schema enforcement is error-prone — past four files contained eight independent schema violations.

Use when generating Tagespuls Slot 2 / Slot 3 or Tagesdeutung (Phase 2) for Bazodiac. Operates on top of curated aphorism pool — never generates Slot 1. Enforces modus-abhängige Logik (pulse / trace / spannung) and the Rat-der-sechs constraints from PROMPT_MODULE_DAILY_HOROSCOPE.md.

Internal ClaudeMap runtime for turning a repository into a live architecture map and driving that map during walkthroughs. Prefer the public commands in .claude/commands for normal use.

Identify distinct software components from design artifacts and create per-component directories. Use when transitioning from Design to Code phase.

Draft or update design documents based on approved objectives. Use when translating requirements into technical specifications. Covers architecture, data model, API design, and design completeness assessment.

Interactive requirements elicitation for the Objectives phase. Use when defining, reviewing, or modifying stakeholders, goals, user stories, requirements, assumptions, or constraints. Also performs gap analysis on existing artifacts.

Execute the next pending task from the implementation plan. Finds the first actionable task, derives its actual scope, implements with tests, handles design gaps, and updates task status. Use during the Code phase to make incremental progress.

Apply a user-reported fix, bug correction, or change to one or more components. Gathers context interactively, identifies affected components, builds informative context from design artifacts and decisions, implements the fix with tests, and handles design gaps. Use during the Code phase or later.

Create a phased implementation plan from design artifacts. Populates tasks.md with short tasks grouped into incremental development phases, each ending with a deployable/testable system. Use after SDLC-decompose, before coding begins.

Guided project initialization for the SDLC scaffold. Use when setting up a new project or re-configuring an existing one. Sets the project description in CLAUDE.md so AI agents have the right context from the start.

Project-wide status dashboard across all SDLC phases. Use when the user wants an overview of the entire project state. Aggregates artifact counts, statuses, phase gate readiness, traceability health, and assessment freshness into a single report.