Sssdd Code

Rules

• Be concrete enough that implementation can start.
• Keep traceability back to earlier layers.
• Enforce 1 code file = 1 md.
• Write the generated markdown content in Japanese.
• Keep each markdown spec narrowly scoped to its target file.
• Parent Coverage should explain the role this file plays inside its parent module or package.
• Keep file-local naming aligned with 01-glossary.md, using and refining any shared type/class, variable/field, or other identifier hints when they become stable for the tree.
• Operational Notes should capture concrete file-level obligations implied by upstream non-functional requirements, such as logging hooks, audit fields, timeout handling, rate limiting seams, retry boundaries, or metrics emission.
• Show the file tree first when generating many files so the user can react before the layer becomes verbose.
• Update matching file specs in place when the target code file still exists.
• Do not copy large portions of module-design text into every file spec. Keep only the file-local contract.
• If several file specs repeat the same contract, move that contract upward into module-design unless the duplication is required by separate file ownership.
• Use Open Questions only for issues that remain unresolved after the current discussion pass.
• Use Assumptions only for temporary working assumptions adopted after discussion.
• If discussion resolves an item, move it into the main body and remove it from these sections.
• If one module-design node expands into many code files, create one markdown file per code file.
• Public Interfaces, Dependencies, and Test Strategy should be specific enough that implementation can proceed without redesigning file responsibilities.
• Exit Checks should confirm that the target file scope, dependency direction, and test surface are all explicit.

Report

Report:

• target project directory
• code-design files created or updated
• target code files covered
• file tree agreed or assumed
• file-level hooks for non-functional requirements identified
• questions asked or assumptions made
• coverage and exit readiness summary
• recommended next skill: $sssdd-test