skills/magnus919_agent-skills

Fork 0

mirror of https://github.com/magnus919/agent-skills.git synced 2026-09-14 13:06:30 +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.3 KiB

Raw Blame History

Dependency and Handoff Record

Complements the implementation plan template. Fill one record per implementation plan. Each dependency must have an owner and a handoff contract.

Dependency inventory

Hard dependencies (blockers)

A hard dependency blocks progress: the dependent workstream cannot start or complete until the dependency is satisfied.

ID	Dependent workstream	Depends on (workstream / team / system)	What is needed	Owner of dependency	Needed by date	Status
DEP-H1	[WS-N]	[WS-M / team-X / service-Y]	[specific artifact or condition]	[name or role]	[date]	[on-track / at-risk / blocked]

Soft dependencies (preferences)

A soft dependency is preferred but not blocking: the work can proceed without it, but quality, efficiency, or risk profile improves if it is satisfied.

ID	Dependent workstream	Preferred input	Why it helps	Owner	Desired by	Fallback if unsatisfied
DEP-S1	[WS-N]	[design review from team-X]	[reduces rework risk]	[name]	[date]	[proceed without review; accept rework risk]

Critical path

The critical path is the longest chain of hard dependencies from start to completion.

Start → [WS-A] → [WS-B (depends on WS-A)] → [WS-C (depends on WS-A, WS-B)] → Complete
        2 tw          3 tw (blocked without WS-A)        4 tw (blocked without WS-B)
Total critical path: 9 team-weeks

Critical path shifts

Shift	Trigger	New critical path	Impact
[DEP-H3 delayed by 2 weeks]	[team-Y unavailable]	[path shifts through WS-D]	[+2 weeks to total]

Handoff contracts

A handoff contract defines what one team delivers to another and how the recipient verifies it.

Handoff ID	From (team / owner)	To (team / owner)	Artifact	Delivery date	Acceptance criteria	Verification
HND-1	[Team A / name]	[Team B / name]	[API spec, schema, library, config]	[date]	[what makes it acceptable]	[how the recipient verifies]

Cross-repository dependencies

When work spans multiple repositories, each repository boundary is a dependency interface.

Repository	Owned by	Depends on (repository)	Interface contract	Version / SHA	Coordinated release?
[repo-a]	[team]	[repo-b]	[API v2, shared schema v3]	[tag or SHA]	[yes — coordinated / no — independent]

External dependencies

Dependencies on teams, vendors, or services outside the plan's direct control.

Dependency	Provider	Contact	SLA or commitment	Escalation contact	Contingency if unavailable
[third-party API]	[vendor]	[email / Slack]	[uptime SLA]	[contact]	[degrade gracefully, cache fallback]

3.3 KiB Raw Blame History