planning-patterns
Planning Patterns provides a structured methodology for comprehensive project planning that includes research, brainstorming, alternative evaluation, phased planning with acceptance criteria, risk assessment with mitigations, and TDD strategy definition. Use this skill when initiating the PLAN workflow or tackling any task requiring strategic thinking before execution, as it ensures plans flow directly into BUILD execution through documented continuity saved to the plans directory.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/planning-patterns && cp -r /tmp/planning-patterns/library/methodologies/cc10x/skills/planning-patterns ~/.claude/skills/planning-patternsSKILL.md
- Search for existing solutions and patterns - Identify relevant libraries and tools - Find best practices in the domain - Check for known pitfalls ### 2. Brainstorming Phase - Generate at least 3 alternative approaches - Evaluate trade-offs: complexity, time, risk, scalability - Consider build-vs-buy decisions - Rank by feasibility and alignment ### 3. Plan Creation - Structure with phases, tasks, and milestones - Define acceptance criteria per phase - Map dependencies between tasks - Include risk assessment with mitigations - Define TDD strategy per coding phase - Estimate effort and timeline ### 4. Review Gate - Verify completeness against original request - Validate logical phase ordering - Check actionability of risk mitigations - Score plan completeness (>=80 to pass) ## Plan-to-Build Continuity - Save plans to `docs/plans/` directory - Reference plan file in session memory - BUILD workflow reads plan during requirements clarification - Component-builder follows documented phases ## When to Use - PLAN workflow (primary) - Any task requiring strategic thinking before execution ## Agents Used - `planner` (primary consumer) - `github-researcher` (research phase)
Coordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
>-
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.