pkasarda/pkasarda-skills
Agentic Engineering Kit: project bootstrap, discovery, architecture, authorization, test-first change delivery, production UI, reliable effects and verification.
Set up a new repository or onboard an existing project for agent-assisted work, connecting project context, specs, issue handoffs and progressively disclosed instructions. Use for project bootstrap or instruction/workflow onboarding. A bounded feature, bug or copy edit should use its normal delivery procedure without repeating bootstrap.
Design, implement or review access policy for protected resources and operations. Use for new protected entrypoints, roles, ownership or tenant scope, field visibility, sharing links, delegated jobs and permission changes. Authentication alone does not settle access; visual-only edits need no authorization review.
Deliver a scoped feature or bug fix from its accepted contract through test-first implementation, independent review and verified handoff. Use when asked to implement or finish a change and no project-specific delivery workflow already owns it. Read-only advice, discovery-only work and trivial copy edits do not need this workflow.
Verify a change or claim with discriminating evidence at the actual affected boundary. Use when planning validation, reviewing weak tests, diagnosing false-green results, or deciding whether behavior is verified. Keep checks proportional; trivial edits do not require a full test programme.
Assess whether an issue, epic or proposed slice is current, owned and ready for action. Use before planning implementation from a backlog or reconciling stale specifications and overlapping work. Assessment is read-only unless the user separately authorizes tracker changes.
Shape an unclear product idea or new capability into a small, testable user flow and a decision-ready brief. Use when the audience, core job, scope or success is unresolved. A sufficiently specified implementation task should proceed through normal delivery without another discovery ceremony.
Build or assess data-backed UI for complete, reachable results and truthful asynchronous behavior. Use for lists, filters, database-backed pickers, forms and workflows that must work beyond demo data. Keep static copy or visual-only changes local; this is not a replacement for visual design.
Design, implement or debug recoverable asynchronous work and external side effects. Use for delivery, queues, retries, uncertain provider outcomes and compensation. It does not require a queue or outbox for every function or replace the domain owner of the underlying operation.
Design or challenge software architecture from concrete flows, invariants, ownership and failure evidence. Use for new system design, unclear module boundaries, cross-cutting bug clusters, or changes to state, authority, history or external-effect contracts. Keep ordinary local fixes local; this is not a mandatory architecture ceremony for every edit.
Implement or review a bounded state-changing operation with authoritative scope, lifecycle, consistency and truthful results. Use for database or durable-state mutations, transitions and coupled writes. Architecture discovery and ordinary local presentation edits are separate tasks.