Produce and register an architecture and design artifact, grounded in approved inputs and the codebase, for the design step or any step that chose this skill.
Install
npx skillscat add ashokraj2011/singularityflow/sflow-design Install via the SkillsCat registry.
SKILL.md
Architecture and design
Output contract: Use governed inputs and pinned clarification; publish/show configured artifacts. For suggested actions, pair Shell with the returned Copilot command; honor commandGuidance. If absent, say "Copilot: no verified equivalent"; never invent a slash command.
Boundary: singularity-flow session current --json → ready/workId, cwd=repositoryPath; use CLI/workItemRoot paths; never $HOME.
- For the Boundary
phase, runsingularity-flow phase show <phase> --json. IfpolicyVerifiedis false, showpolicyReason; stop. Continue only ifeffectiveAuthoringSkillis/sf-design, or/sf-phasewithauthoringSkillnull and<phase>=design; else showNext in Copilot:effectiveAuthoringSkillandTerminal equivalent: singularity-flow prepare <phase>, or that a null route drafts nothing; stop. Its governed workflow is Story context. - Run
singularity-flow wm compose --phase <phase>and use its complete prompt. If WM is missing/unreachable/stale, continue with zero-context evidence and repository access; show recovery as optional, never prerequisite. Never derive--taskfrom Story text. Use available architecture/security evidence. - Read the approved inputs the composed prompt names and relevant uploads; inspect grounding-selected source.
- Run
singularity-flow clarification status <phase> --json. Foroff, do not ask or record; continue. Forwhen-needed, ask and record only for material ambiguity; otherwise continue. Forrequired, useask_useronce, wait and record before preparation; if unavailable, display the questions and stop; even when evidence looks complete, confirm boundaries, contracts, failures, and tradeoffs. Record viasingularity-flow clarification record <phase> --response-file <file>. - Run
singularity-flow prepare <phase>and complete the returned document. - Cover components, interfaces, data flow, alternatives, compatibility, security, privacy, observability, migration, rollout/rollback, risks, and implementation order.
- State assumptions and tradeoffs. Do not implement production code.
- Run
singularity-flow phase draft-check <phase> --json, thensingularity-flow phase prepublish <phase> --json. If unready, run read-onlysingularity-flow recover <WORK-ID> --phase <phase> --json; stay in this phase. Correct every agent finding now from governed evidence only whencorrection.sameTurn; otherwise route to its owner/regenerator. Recheck up to three changed fingerprints and stop on an unchanged fingerprint. Never blindly delete markers, invent facts or padding, invoke a nested model, or overwrite another producer. - Only when prepublish
statusisready, publish with its exact configured producer/channel. Race-timeARTIFACT_AUTHORING_INCOMPLETE: recheck once, retry once if ready, never loop. Never submit or approve. - Run
singularity-flow phase show <phase> --json; retaindisplayBindingandreviewBinding. Reuse bodies only from a complete visible same-chat display with exactly matching non-nulldisplayBinding. Otherwise reproduce every published text document in full: ID/kind/path/bytes/generation/SHA-256 and--- BEGIN <path> ---/--- END <path> ---. New chat, changed/null binding, omissions or truncation require full display. Tool output or summaries are not review. Binary: path/metadata/open instruction. Show the currentreviewBinding; body reuse never reuses approval consent. - Report commit and tokens. End with each returned
handoff:Next in Copilot: /sf-…from itscopilotCommand, thenTerminal equivalent: singularity-flow …from itscommand; do not submit or approve.