skills/magnus919_agent-skills

Fork 0

mirror of https://github.com/magnus919/agent-skills.git synced 2026-09-12 20:16:29 +03:00

Files

T

f82515e85d feat(implementation-planning): add implementation planning skill (#217 )

Add a reusable implementation-planning skill for turning approved
requirements or specifications into executable, dependency-aware delivery
plans. Covers work breakdown into vertical slices, dependency mapping with
critical-path analysis, ownership assignment, sequencing and parallelism,
staged rollout strategy with rollback paths, and verification traceability
against the original requirement.

Includes:
- SKILL.md with valid frontmatter, entry gate for prerequisite approval,
  progressive-disclosure file map, and handoff table to specialist skills
- README.md with all five required human-facing sections
- references/discovery-brief.md comparing existing planning material and
  defining ownership boundaries
- templates/ for implementation plan, dependency record, and risk/decision/
  verification sections
- evals/evals.json with six output-quality cases covering ambiguous
  requirements, cross-repository dependencies, data migration, risky
  rollout, unapproved prerequisite rejection, and multi-team ownership
  conflict
- Catalog and routing updates (README, skill-triggers, generated catalogs)

Closes #186

Co-authored-by: username <username>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

2026-08-02 17:29:00 -04:00

3.2 KiB

Raw Permalink Blame History

Risk, Decision, and Verification Record

Complements the implementation plan template. Fill one record per implementation plan.

Risk register

ID	Risk description	Severity (1-5)	Likelihood (1-5)	Impact	Mitigation	Owner	Status
RSK-1	[what could go wrong]	[1-5]	[1-5]	[blast radius, what depends on this]	[what reduces likelihood or impact]	[name]	[open / mitigated / accepted]

Risk heatmap notes

Severity 4-5: requires explicit mitigation and escalation path.
Likelihood 4-5: requires a contingency plan with trigger condition.
Both severity and likelihood >= 4: flag for leadership review before plan approval.

Decision log

Resolved decisions

ID	Decision	Options considered	Chosen	Rationale	Decided by	Date
DEC-1	[what was decided]	[A, B, C]	[B]	[why B over A and C]	[name or role]	[date]

Unresolved decisions

ID	Decision needed	Options	Blocked by	Impact of delay	Owner	Deadline	Status
DEC-U1	[what must be decided]	[A, B]	[waiting on architecture review]	[blocks WS-3 start]	[name]	[date]	[open / escalated]

Assumptions register

ID	Assumption	Basis (evidence or guess)	Valid until	Owner	If invalid...
ASM-1	[what we assume to be true]	[data, precedent, or explicit guess]	[date or milestone]	[name]	[what changes]

Verification checklist

Trace every requirement from the approved input to a verification activity.

Requirement ID	Requirement summary	Workstream	Acceptance criterion	Verification method	Verifier	Evidence artifact	Status
REQ-1	[from approved spec]	[WS-1]	[testable condition]	[automated test / manual review / demo / monitoring]	[name or role]	[test report, review sign-off]	[pending / passed / failed]

Verification methods reference

Method	When to use	Evidence
Automated test	Deterministic behavior	Test run output, CI pass
Manual review	Subjective quality, UX, docs	Reviewer sign-off
Demo / walkthrough	Integrated behavior across teams	Demo recording or notes
Production monitoring	Rollout health, SLO compliance	Dashboard screenshot, alert silence
Data reconciliation	Migration correctness	Row counts, checksums, diff report

Rollback verification

For each rollout stage, verify that rollback works before proceeding.

Stage	Rollback test performed?	Rollback time (actual)	Data integrity verified?	Signed off by
Stage 1	[yes / no]	[minutes]	[yes / no]	[name]

3.2 KiB Raw Permalink Blame History