docs: prd-agent-consolidation - Record target and actual skill count #3194

Documentation Update Summary

Spec Kit task: T060. Record the verified target and actual consolidated skill counts explicitly in SC-001 of .github/specs/001-prd-agent-consolidation/spec.md, preserving the success criterion and its evidence trail.

Linked Stories/Tasks/PRs/Epic

• Depends on T059, #3193.
• PR #2865 is cited by the consolidation records as the Phase 3 merge.
• Linked Linear issue: LS-4015.

Milestones & Timeline

Phase 6 polish, after the T059 count and any discrepancy have been verified. No separate deadline is established.

What documentation is needed?

In SC-001, state both the target and evidence-backed actual count. The task list and decision log currently report 28 for each, but SC-001 does not yet record them as separate values.

Why is this documentation important?

The success criterion should distinguish the intended inventory from the measured inventory so future maintainers can identify drift rather than read the target as proof of completion.

Acceptance Criteria

• T059 evidence checked against the current agents/prd-agent/skills/ inventory.
• SC-001 states both target and actual counts; any mismatch links to the documented analysis rather than being excused by changing the target.
• Wording aligns with DECISIONS_LOG.md and the task list.
• Documentation is clear, accurate and up to date.
• Code examples or screenshots included if applicable.
• Documentation is accessible and easy to find.
• Changelog entry prepared for a PR if the update is user-facing.
• Correct branch prefix used for a PR (docs/).
• PR description updated with relevant details.
• Labels and types match organisation standards.

Additional Context

The tasks file calls T060 complete. Verify the missing explicit target-and-actual wording before deciding whether this is a correction or was delivered elsewhere.

Definition of Ready (DoR)

• Documentation need is clear and well defined.
• Related documents, issues or files linked.
• Acceptance criteria listed.
• Estimate added if relevant.
• Milestone or release assigned if applicable.

Definition of Done (DoD)

• Documentation meets organisation standards and guidelines.
• Changelog entry prepared for a PR if applicable.
• Documentation reviewed for clarity and accessibility.
• Screenshots or code examples included if relevant.
• PR uses the correct branch prefix (docs/) and applicable PR template.
• Branch deleted after merge, if applicable.
• Linked issues updated with the latest status and closed only when their own completion is verified.
• Related epic updated rather than closed solely because this issue is completed.