skills/magnus919_agent-skills

Fork 0

mirror of https://github.com/magnus919/agent-skills.git synced 2026-09-11 19:47:12 +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

4.6 KiB

Raw Permalink Blame History

Implementation Plan: [plan name]

Based on approved [spec / requirement / decision record], approved by [approver name or role] on [approval date].

1. Work Breakdown

Workstreams and vertical slices

Each workstream is a vertical slice — an end-to-end deliverable that provides independent value. Prefer vertical slices over horizontal layers.

ID	Workstream	Description	Completion criterion	Owner	Estimated effort
WS-1	[name]	[what this delivers, end to end]	[observable condition that means it is done]	[name or role]	[team-weeks]
WS-2	[name]	[...]	[...]	[...]	[...]

Workstream detail

WS-1: [workstream name]

Scope: [what is in and explicitly out of scope]
Dependencies: [what this workstream needs from others, with owners]
Acceptance criteria: [testable conditions that define done]
Verification: [how completion will be verified against the original requirement]

2. Dependency Map

Complete the dependency record for the full dependency graph. Summarize key dependencies here.

Critical path

The critical path is the longest chain of dependent work that determines the earliest possible completion.

_[WS-A] → [WS-B] → [WS-C] = critical path of N team-weeks_

Dependency interfaces

From	To	What	Contract (API, schema, event)	Hard or soft
[WS-X]	[WS-Y]	[description]	[the interface artifact]	[hard / soft]

3. Sequencing and Parallelism

Phase	Workstreams (concurrent)	Depends on	Duration	Synchronization gate
Phase 1	[WS-1, WS-2 (parallel)]	[none]	[N weeks]	[what must be true to exit phase 1]
Phase 2	[WS-3 (sequential after WS-1)]	[WS-1]	[N weeks]	[...]

4. Ownership and Coordination

Role / Team	Owner	Workstreams owned	Coordination mechanism
[team name]	[name]	[WS-1, WS-3]	[sync meeting, Slack channel, dashboard]

Cross-team coordination

Integration checkpoints: [when cross-team work is verified together]
Escalation path: [who to escalate to if a dependency is blocked]
Communication cadence: [how often teams sync, what artifact tracks status]

5. Rollout Strategy

Rollout stages

Stage	Scope (who gets it)	Duration	Gate (condition to proceed)	Observability signal	Rollback trigger
Stage 1	[internal / 1% / single region]	[N days]	[e.g., error rate < 0.1%, p95 latency < baseline +10%]	[dashboard, alert]	[specific condition]
Stage 2	[10% / beta users]	[N days]	[...]	[...]	[...]
Stage N	[100%]	—	—	[...]	—

Rollback plan per stage

Stage	Rollback procedure	Data rollback	Time to rollback	Post-rollback state
Stage 1	[how to revert]	[yes/no, how]	[minutes]	[what the system looks like after rollback]

For data migrations

Dual-write / backfill strategy: [how the transition period works]
Schema compatibility: [forward-compatible, backward-compatible, or breaking]
Cutover procedure: [step-by-step cutover]
Reconciliation: [how to verify old and new data match before cleanup]

6. Verification Traceability

Requirement (from approved input)	Workstream	Acceptance criterion	Verification method	Verified by
[REQ-1 from spec]	[WS-1]	[testable condition]	[test, demo, review]	[name or role]

7. Unresolved Decisions and Risks

ID	Description	Impact	Owner	Resolution deadline	Status
DEC-1	[open decision]	[what depends on it]	[name]	[date]	[open]
RSK-1	[risk]	[severity, likelihood]	[name]	[date]	[open / mitigated / accepted]

8. Assumptions

Assumption	Made by	Date	Valid until	If invalid...
[assumption]	[name]	[date]	[date or event]	[what changes in the plan]

4.6 KiB Raw Permalink Blame History