Convert approved specs into executable plans with ownership and verification.
npx skills add https://github.com/GanyuanRan/Aegis --skill writing-plans-ganyuanran
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/GanyuanRan/Aegis/tree/main/skills/writing-plans Command: npx skills add https://github.com/GanyuanRan/Aegis --skill writing-plans-ganyuanran
Managing complex multi-step tasks from an approved spec can be error-prone and time-consuming. This skill automates turning high-level requirements into a concrete, executable plan with clearly defined ownership, boundaries, and verification criteria.
Provide approved requirements, a Spec Brief, or a Design Spec, and I will generate a complete implementation plan saved under docs/aegis/plans with bite-sized tasks.
High-intent search queries and answers about installing and using this skill.
Spec conversion to executable implementation plans requires task decomposition, scope definition, and evidence-based checkpoints. This process transforms approved requirements into structured planning artifacts with clear ownership boundaries and verification steps saved under docs/aegis/plans.
Task decomposition for cross-team workstreams is the breakdown of approved specs into bite-sized tasks with explicit file ownership and governance steps. It ensures multidisciplinary teams have structured verification and architecture integrity boundaries during implementation.
Preventing scope creep during design spec planning involves applying plan-time checks, scope boundaries, and risk assessment. Generating compact plan artifacts with baseline authority references ensures implementation stays within approved governance signals.
Yes, this planning approach supports multidisciplinary workstreams with cross-team ownership. It converts high-level briefs or design specs into complete plans requiring documented outputs, compatibility boundaries, and structured verification steps.
Implementation governance for complex tasks is best structured by generating compact plan artifacts that preserve traceability to baseline authorities. This includes documented plan outputs, governance signals, and structured verification steps to guide execution.
Implementation plans lack clear ownership and verification criteria when approved specs are not decomposed into tasks with explicit boundaries. Converting specs into executable planning artifacts adds file ownership, risk mitigation, and testable deliverable checkpoints.
yknothingPlan high-level architecture and component boundaries from reviewed requirements.
vobbilisCreate detailed implementation plans with prerequisites and verifiable tasks.
lionbenjaminValidate technical implementation plans for architecture, security, and operational readiness.
djwmobleyDecompose specs into actionable implementation plans with traceability.
