plan-task

To create an implementation plan from a vague Jira ticket, the skill enforces a structured intake process that clarifies scope boundaries, acceptance criteria, and dependencies before development begins. It captures all relevant constraints and produces documented planning outputs.

Documenting requirements before feature development requires a disciplined intake process that aligns stakeholders and captures constraints. This skill provides a clarification checklist to enforce scope boundaries and logs decisions for future auditing before any code is written.

Yes, you can use this planning process for AWS CDK and multi-repo changes. It reviews repo-specific conventions and performs AWS readiness checks, delivering documented planning outputs that include CDK enrichment when needed for your feature or bug planning.

To structure a clarification checklist for software changes, you need to enforce scope boundaries, acceptance criteria, affected repos, blockers, and dependencies. This skill applies this checklist to guarantee all relevant information is captured before proceeding to implementation.

Yes, this intake process works with markdown briefs and epic context. It applies a structured intake process across development repositories needing feature or bug planning, guaranteeing all relevant information and constraints are captured from your provided briefs.

You need documented decisions and acceptance tests before coding to align stakeholders and ensure each acceptance criterion is verifiable. This skill produces concrete implementation plans with decision logs for future auditing, preventing scope creep during development.