← ClaudeAtlas

project-initlisted

Framework for creating project documentation from specs — reviews, research, architecture, planning, task decomposition into slices, and optional Jira sync. Triggers on "storm the spec", "analyze spec", "project init", "init project from spec", "проанализируй ТЗ", "разбери ТЗ", "создай документацию по ТЗ", or when user wants to turn a spec into structured project documentation. Also use when user asks to "break down a spec", "create PRD from spec", "plan implementation from requirements", or any workflow that converts a specification into actionable project docs with phases.
UnBergant/bergant-workflow · ★ 5 · AI & Automation · score 81
Install: claude install-skill UnBergant/bergant-workflow
# Project Init ## Routing **`status` (or no arguments):** execute INLINE — read `docs/spec-state.json` and display the phase table. Do NOT launch an agent. See "Status Display" below. This skill's directory (its reference files live here) — resolved at runtime: !`echo ${CLAUDE_SKILL_DIR}` **All other commands** (`start`, `complete`, `recover`): launch `Agent(general-purpose)` with the prompt below. Replace `SKILL_DIR` with the absolute path printed just above: ``` Read the project-init skill: - Commands and rules: SKILL_DIR/SKILL.md (from "## Agent Instructions") - Phase execution details: SKILL_DIR/references/phases.md (read ONLY the active phase section) Execute command: $ARGUMENTS State file: docs/spec-state.json Project root: $CWD Read existing docs/ artifacts for context before acting. Follow all instructions. When you hit a user gate, return findings, options, and what needs discussion. Be concise. ``` If the agent returns an error, display it without re-running. ## Status Display Read `docs/spec-state.json`. If missing: "No active spec analysis. Use `/bergant-workflow:project-init start <spec-file>` to begin." Display formatted table: - Each phase with status (pending, in_progress, completed) - Current phase highlighted - User gates marked - Next action needed --- ## Agent Instructions You manage the spec-to-documentation framework. State persists in `docs/spec-state.json`. **Core principle:** Be interactive. Present options, trade-offs, recommendations.